Only because until you've got the key in place, you need to use a password. However, if you've got the keys in the correct direcctory/file, and have the correct permissions on that directory/file, you shouldn't have to use a password even once, if memory serves. On Mon, 22 Nov 2004, Harry Hoffman wrote: > Sorry, I'm a little late on this thread. But you have to login at least > once interactively before it will no longer ask for a password, right? > > Pete Nesbitt wrote: > > On November 22, 2004 06:04 am, Jithesh wrote: > > > >>Hi all, > >> > >>I was able to create successful login for the root account from a remote > >>client with the help of the public key and the authorized key. But when > >>I tried to do it for a normal account it still asks for the password. > >> > >>Here is what I have done > >>1. Generated the public key in the client machine. > >>2. Copied the same into the server's normal user account's > >>~/.ssh/authorized_keys > >>3. Changed the permission to read only for the file authorized_keys > >> > >>I did the same thing for the root account and it worked but not or other > >>users. > >> > [snip... sorry Pete :-) ] > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a message to: site-update-request@xxxxxxxxxxxxxxxxx with a message of: subscribe -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
