On Wednesday 26 September 2007, Herbert Laubner wrote: > I want to connect to another machine in my local network using ssh. > Somehow I do not get it managed to write the fingerprint to the > .ssh/known_hosts because of missing rights. > > [EMAIL PROTECTED] ~ $ ssh 192.168.0.50 > The authenticity of host '192.168.0.50 (192.168.0.50)' can't be > established. RSA key fingerprint is > c5:1f:98:93:f3:30:01:b1:95:3e:30:40:47:ef:97:35. Are you sure you > want to continue connecting (yes/no)? yes > Failed to add the host to the list of known hosts > (/home/herbert/.ssh/known_hosts). > Password: > Last login: Wed Sep 26 20:37:42 2007 from 192.168.0.20 > Welcome to Darwin! > rlbk-hmbg-de01:~ herbert$ exit > logout > Connection to 192.168.0.50 closed. > > [EMAIL PROTECTED] ~ $ ls -al /home/herbert/.ssh/ > ls: Zugriff auf /home/herbert/.ssh/. nicht möglich: Keine > Berechtigung ls: Zugriff auf /home/herbert/.ssh/known_hosts nicht > möglich: Keine Berechtigung > ls: Zugriff auf /home/herbert/.ssh/.. nicht möglich: Keine > Berechtigung insgesamt 0 > d????????? ? ? ? ? ? . > d????????? ? ? ? ? ? .. > d????????? ? ? ? ? ? known_hosts
Ouch. That's file system corruption. You need to fsck that disk right now. I once saw similar stuff on a reiser filesystem and the only thing that helped was --rebuild-tree. Good luck on your end. > I think, it has to be a stupid mistake. I did > windose ~ # chown herbert /home/herbert/.ssh > windose ~ # chgrp users /home/herbert/.ssh > > but this did not help?? Two reasons: 1. You only chowned the directory itself, not the files in it. What you probably wanted was chown -R herbert:users /home/herbert/.ssh 2. The filesystem metadata is corrupt, so you wont be able to do anything in that directory anyway. alan -- Optimists say the glass is half full, Pessimists say the glass is half empty, Developers say wtf is the glass twice as big as it needs to be? Alan McKinnon alan at linuxholdings dot co dot za +27 82, double three seven, one nine three five -- [EMAIL PROTECTED] mailing list
