On Tue, 2007-10-30 at 11:22 -0500, Daniel Kuecker wrote: > I tried both keys and both failed. when I look at the client file it appears to be the nomachine key. is there a way to reset the keys? > > >>> Nils Breunese <nils breun nl> 10/29/07 4:51 PM >>> > Craig White wrote: > > > protocol 1 would use authorized_keys > > protocol 2 would use authorized_keys2 > > > > I am no expert on this stuff but that is my understanding. > > This used to be the case, but is not generally true anymore. This > depends on your distribution I believe. On Red Hat / CentOS / Fedora > you can just use authorized_keys for protocol version 2. I don't know > if you have to add the '2' on Debian / Ubuntu, but I usually see > authorized_keys2 in howto's for Debian / Ubuntu. Maybe it works > without the '2' on those distributions as well, I don't know. The authorized_keys used is defined in /etc/ssh/sshd_config as the line: AuthorizedKeysFile .ssh/authorized_keys > > Nils Breunese. > > > > > > _______________________________________________ > K12OSN mailing list > K12OSN redhat com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see <http://www.k12os.org> > -- James P. Kinney III CEO & Director of Engineering Local Net Solutions,LLC 770-493-8244 http://www.localnetsolutions.com GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <jkinney localnetsolutions com> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
Attachment:
signature.asc
Description: This is a digitally signed message part