similar to: failure to attempt protocol v1 connection with v1 key

I expect this is user error, but I thought I'd post in case anyone else is feeling a similar sense of losing their mind. I have a root cron job: 0 3 * * * rsync -Hva --stats --del ... / /media/2tb/bak/dancer-`date +\%F`/ "..." represents 4 --link-dest's and 22 --exclude's (including /media/). So last night, / should have been copied to

rsync -Ha --link-dest=/media/4tb/bak/panic-2012-01-01 /media/2tb/bak/panic-2012-02-01 /media/4tb/bak/ root at dancer:/media/4tb/bak# ls -l panic*/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2011-12-20/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2012-01-01/home/darxus/0000_latest.jpg -rw------- 1 darxus darxus

https://bugzilla.samba.org/show_bug.cgi?id=10233 Summary: rsync is spending a lot of time lstat64()'ing --exclude'd files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugs.freedesktop.org/show_bug.cgi?id=48074 Bug #: 48074 Summary: 3D / OpenGL clients used with wayland always cause an immediate hang Classification: Unclassified Product: Mesa Version: 8.0 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium

I'm watching my backup via rsync, throttled to a very low speed. Looks like downloading apache logs is taking the longest time (when I'm rsyncing over an old copy of the same data) because it's not noticing that, for example, www.chaosreigns.com-access.log.196.gz on the origin is the same file as www.chaosreigns.com-access.log.186.gz on the destination, so *everything* is getting

I have legitimate ssh access to two remote machines. ssh directly from either machine to the other is blocked by firewalls which I cannot control. $ rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/ receiving file list ... done rsync: mkdir user@host2:/tmp: No such file or directory rsync error: error in file IO (code 11) at main.c(319) I would like this to copy host1:/tmp/dir into

https://bugs.freedesktop.org/show_bug.cgi?id=55596 Priority: medium Bug ID: 55596 Assignee: nouveau at lists.freedesktop.org Summary: weston-launch causes graphical corruption / lockup Severity: major Classification: Unclassified OS: Linux (All) Reporter: vekinn at gmail.com Hardware: x86-64 (AMD64)

https://bugzilla.mindrot.org/show_bug.cgi?id=2123 Bug ID: 2123 Summary: does not seem to support sftp protocol version 5 rename flag for overwriting files Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5

Hi, I'm wondering if this code from the "Writing R Extensions" manual is really safe: SEXP mkans(double x) { SEXP ans; PROTECT(ans = allocVector(REALSXP, 1)); REAL(ans)[0] = x; UNPROTECT(1); return ans; } double feval(double x, SEXP f, SEXP rho) { defineVar(install("x"), mkans(x), rho);

I have been searching the archives and confused about some points that I am hoping could be cleared up. RSA versus DSA I seem to see a lot of messages saying this. That DSA is slow. DSA was added only to avoid a patent which is now expired. RSA is the preferred authentification method. DSA should be avoided. Which all sounds fine to me and I think I agree with that. Assuming this applies

http://bugzilla.mindrot.org/show_bug.cgi?id=231 Summary: ssh-keygen has fatal error while updating comment in RSA1 key Product: Portable OpenSSH Version: 3.1p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo:

https://bugzilla.mindrot.org/show_bug.cgi?id=2513 Bug ID: 2513 Summary: Do not mention rsa1 key type in ssh-keygen usage & in manual pages Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement

https://bugzilla.mindrot.org/show_bug.cgi?id=2505 Bug ID: 2505 Summary: key_load_private_type: unknown or unsupported key type Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: ssh Assignee: unassigned-bugs at

Hello fellow OpenSSH workers, I have encounter this when I was installing OpenSSH: Generating public/private rsa1 key pair. Your identification has been saved in /etc/ssh_host_key. Your public key has been saved in /etc/ssh_host_key.pub. ****************************************************** Generating public/private dsa key pair. Bus Error - core dumped

There is a program called VNC (virtual network computing -- http://www.uk.research.att.com/vnc/) which is basically an opensourced cross-platform replacement for pc anywhere type software. It's excellent. But it's authentication is lacking. It asks for a single password, and has no support for usernames (at least none that is useful to me). VNC is distributed under the GPL. Sanba has

For what it's worth--only minimal time spent trying new version. Bug: OpenSSH-2.5p1 does not find version 2 host key in directory specified by sysconfdir in configure. Env: Redhat Linux 6.2- kernel 2.2.18- Alpha ev5 processor- Compaq XP1000- egcs-2.91.66 sysconfdir=/etc/openssh Testing is on single host using ssh2.5p1 to connect to sshd2.5p1. Symptom: [root at penguin sbin]# sshd -d

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We recently upgraded to OpenSSH 4.2p1 with the chroot patch supplied on sourceforge. Since then, we've noticed odd problems with random client failures. Today I wrote little scripts to keep restarting sshd with the - -ddd flag and finally captured what's going on, I believe. First, openssh is compiled as so: OpenSSH_4.2p1, OpenSSL

The manual page for ssh-keygen says: "For RSA1 keys, there is also a comment field in the key file this is only for convenience to the user to help identify the key." It seems though that RSA2 and DSA keys also have comment fields, not just RSA1. Is this just an error in the documentation? Also the documentation says that only RSA1 key comments can be changed with ssh-keygen's

http://bugzilla.mindrot.org/show_bug.cgi?id=746 Summary: host authentication requires RSA1 keys Product: Portable OpenSSH Version: 3.7p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Documentation AssignedTo: openssh-bugs at mindrot.org ReportedBy:

Hello, I am attempting to make public key authentication to work between OpenSSH 3.0.2 client on OpenBSD and SSH-1.99-OpenSSH_2.9 FreeBSD localisations 20011202. From reading sshd -ddd and ssh -v I can't figure out what goes wrong. Could somebody interpret the attached typescripts for me, please? Here's the relevant part from the server log and I don't understand it: debug2: