Basics of key authentication
From: OpticTygre (optictygre_at_adelphia.net)
Date: 07/25/04
- Previous message: Jacob Nevins: "Re: PuTTY + compression = possible?"
- Next in thread: Anne & Lynn Wheeler: "Re: Basics of key authentication"
- Reply: Anne & Lynn Wheeler: "Re: Basics of key authentication"
- Reply: Richard E. Silverman: "Re: Basics of key authentication"
- Reply: Jonathan: "Re: Basics of key authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 25 Jul 2004 00:37:43 -0400
Ok, so everything I've read basically tells me the client creates a public
and private key. The public key gets copied to the server, and when the
client wants to log in, the server encrypts some message with the public
key, and the client decrypts it with its private key to prove he is who he
says he is. Is that right so far?
Alright, if that's ok, then I have a few questions.
1. A server can have tons of public keys stored on it. How does he know
which public key to encrypt the message with for the client?
2. In the process of public / private key authentication for logins, what
is the order things are typically done? IE:
a. client says "hey, I want to connect"
b. client sends a message encrypted with private key
c. server decrypts through list of public keys
etc..... (I'm sure the above isn't right)
In other words, what's the step-by-step process used for authenticating via
public/private keys between client and server? Thanks for helping to clear
things up.
-Jason
- Previous message: Jacob Nevins: "Re: PuTTY + compression = possible?"
- Next in thread: Anne & Lynn Wheeler: "Re: Basics of key authentication"
- Reply: Anne & Lynn Wheeler: "Re: Basics of key authentication"
- Reply: Richard E. Silverman: "Re: Basics of key authentication"
- Reply: Jonathan: "Re: Basics of key authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|