So if I'm right calling it a 'key' is a misnomer. I am a very literal person. if they call it a key it unlocks things, not creates them. That is where my confusion is from. Am I correct? :-)~MIKE~(-: On Mon, Feb 9, 2015 at 4:57 PM, Michael Havens wrote: > I still don't quite get it. You generate the key with the public key and > does that produce a private key. So the public key never changes? I think > it just dawned on me! The public key must be an algorithm which makes the > private key. > > > :-)~MIKE~(-: > > On Mon, Feb 9, 2015 at 4:37 PM, wrote: > >> There are several 'flavors of keys' (and I am no expert) but I'll tell >> you about keys to ssh without passwords. >> When you: >> $ ssh-keygen >> The program creates a public and a private key. >> You can only decrypt with the private, anyone can encrypt with the public. >> When you locate the public in the appropriate location, you can login >> without password in the other box. >> There are 348695456 configuration variables to this... >> ET >> >> >> Michael Havens writes: >> >>> I read http://www.weegy.com/home.aspx?ConversationId=0E113805 >>> So, what I am guessing is that there is a public key on the computer that >>> is sending the information to encrypt the data and (for security) you >>> have >>> another key to decrypt the data. But I suppose that the sender must have >>> the receivers key as well so it isn't really more secure. >>> :-)~MIKE~(-: >>> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > >