Did you create public/private keys with ssh-keygen? Did you copy the public key to each machine you want to access? Here's how I do that. I cat every .pub key I have into a single authorized_keys file and copy this single file to all the machines I use. That's item one. Item two is that you can get a very detailed listing of the ssh negotiation with the -v argument. More instances of -v means more verbose detail, e.g. ssh -v -v -v 10.0.0.1 igueths at comcast.net writes: > From: "igueths at comcast.net" <igueths at comcast.net> > > Hi all. I recently configured sshd properly, or so I thought. I currently > don't have physical access to my machine so I figured I would login and > check a few things. However, I was greeted with the unpleasantness of not > being able to login to your own box. Sshd kept denying access when I > entered the correct username/password. Only 1 person was able to get access > via ssh, and he had to re-enable telnet so I could access sshd_config and > figure out what was happening. I compared my sshd_config to one present on > a working ssh config, and found that most of the params were set to default > values, except for some path settings. I am currently running the latest > openssh. Does anyone have any idea why sshd would exhibit such behavior? > Currently I have Passwordauthentication set to yes and pam authentication > set to no. Anyone have any ideas on this one? > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web.com/ . > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175
