Op zaterdag 24 september 2011 09:28:51 schreef Juergen Harms: > I need password-less ssh between all Linux systems on my LAN. Worked > great until some weeks (?) ago. Still works for opening sessions from my > laptop to run on the server. But when the server opens a session on the > laptop, all at sudden a password is required. > > My configuration is slightly complex: my systems are multi-boot with > several OS-partitions (for instance to ease coexistance between the > production system and cauldron). To simplify key management, I keep the > key files in a template-directory in a shared (non-OS) partition, > replacing the files in $HOME/.ssh by symbolic links to files in that > directory (and, the server and the laptop are configured as identical as > possible, in particular, same ssh_config and sshd_config files). > > I can make (sounds easy, was quite a loss of time to find out) the > problem come and go by having $HOME/.ssh/authorized-keys as a link into > the shared directory (come), or using a copy of the template file (go) - > as said, the problem only appears on the laptop (and no problem having > the public and private key files implemented as links). Note: the > permissions are ok (0600 for the private key file and for authorized keys). > > For the user that is a regression - is this a bug to be filed?, is it > due to some security enhancement and just bad luck?
so, what exactly is different, can you do an ssh -v to check? is the authorized keys file still linked? is the known_hosts file still ok?
