search for: authorised_keys

Hi, here's a minor and easy to fix bug. Thanks for fixing: > Manual for ssh-copy-id claims public key will be appended to remote file > ~/.ssh/authorised_keys, which should read ~/.ssh/authorized_keys ('s'->'z'). Ciao Christian -- Debian Developer and Quality Assurance Team Member 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853

...the remote /home/mirror, perfect ;) Then, i would like to run it over SSH port 2222 rsync -avz --rsh='ssh -p2222' /home/foor/bar/ mirror@myrsyndserver:mirror/ Still works fine ;) But my user can login in my box with SSH. So, after a couple of google, i found that i have to edit authorised_keys and put : command="rsync --daemon -vv --server ." ssh-rsa AAAAB3NzaC1............... But now, i have this error : $ rsync -avvvz --rsh='ssh -p2222' /home/foor/bar/ mirror@myrsyndserver:mirror/ opening connection using ssh -p2222 -l mirror myrsyndserver rsync --server...

...thors ignore all contact anyway. Fixed >on my system with a simple bash command: > "alias xssh="unset SSH_AUTH_SOCK; ssh". Or you could put the unset into .ssh/rc, or if you use a key to connect from JuiceSSH to machine1 you could add the restrict keyword to the corresponding authorised_keys line (and then unrestrict anything else you actually need). bye, //mirabilos -- 15:41?<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

...lace the .pub key into /home/backup/.ssh/authorized_keys and then you could ssh/scp localhost as the backup user and it worked as expected ie automatically authenticated using RSA. In 3.8p1 the behaviour has changed. For root you can do as described above ie if you add roots .pub key to /root/.ssh/authorised_keys you can ssh localhost as root and it will RSA authenticate. For any other user RSA authentication fails when you try to authenticate from/onto localhost. Why this was relevant in my case was simple laziness. I have a backup widget that takes a list of hosts to backup (including the real name of l...

Damien Miller wrote: >This is ssh trying to connect to $SSH_AUTH_SOCK, perhaps JuiceSSH's >agent that you've forwarded. > ... >the sudo is probably clearing $SSH_AUTH_SOCK and so it doesn't >try to connect to it. > >You can simulate this by clearing the environment variable yourself and >see if the hangs persist. > >If it is the forwarded agent, then the

...e mux master). * ssh(1) and sshd(8) now send terminate protocol banners with CR+LF for protocol 2 to comply with RFC 4253. Previously they were terminated with CR alone. Protocol 1 banners remain CR terminated. * Merged duplicate authentication file checks in sshd(8) and refuse to read authorised_keys and .shosts from non-regular files. * Ensure that sshd(8)'s umask disallows at least group and world write, even if a more permissive one has been inherited. * Suppress the warning message from sshd(8) when changing to a non-existent user home directory after chrooting. * Mention th...

...er). * ssh(1) and sshd(8) now send terminate protocol banners with CR+LF for protocol 2 to comply with RFC 4253. Previously they were terminated with CR alone. Protocol 1 banners remain CR terminated. (bz#1443) * Merged duplicate authentication file checks in sshd(8) and refuse to read authorised_keys and .shosts from non-regular files. (bz#1438) * Ensure that sshd(8)'s umask disallows at least group and world write, even if a more permissive one has been inherited. (bz#1433) * Suppress the warning message from sshd(8) when changing to a non-existent user home directory after chroo...

...er). * ssh(1) and sshd(8) now send terminate protocol banners with CR+LF for protocol 2 to comply with RFC 4253. Previously they were terminated with CR alone. Protocol 1 banners remain CR terminated. (bz#1443) * Merged duplicate authentication file checks in sshd(8) and refuse to read authorised_keys and .shosts from non-regular files. (bz#1438) * Ensure that sshd(8)'s umask disallows at least group and world write, even if a more permissive one has been inherited. (bz#1433) * Suppress the warning message from sshd(8) when changing to a non-existent user home directory after chroo...