> This kind of ad hoc
> thinking by amateurs never results in a protocol worthy of deployment.
>
> The whole concept of encrypting public keys is ludicrous, and it
> doesn't matter what the answers are when you're asking the wrong
> questions.
> __
"Kenneth R. Robinette" <[EMAIL PROTECTED]> wrote:
> From: Bill Browning <[EMAIL PROTECTED]>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: RE: How can I encrypt public key in handshake?
> Date sent:Tue, 20 Mar 2001 15:29:0
> 1. Give your public key to anyone who want its (email what ever..)
> 2. create an SSL connection from client to server.
> 3. Verify that the server is who you think it is (via the public key)
> (client can now trust server)
> 4. Pass an encrypted token to the client (encrypted with client passwo
g her password. Only the correct
client can decrypt the public key, because only the they know the password
it was encrypted with.
--
corky peavy
[EMAIL PROTECTED] - email
(512) 682-6934 x6527 - voicemail/fax
__
FREE voicemail, email, and fax...a
I am building a system that will not use certificates. I'm using the
sample code "mkit" to accomplish self certification.
I do need public/private keys however, and I need the "server" to encrypt
the public key before sending it out. This does not seem to be something
the designers intend the co
I am building a system that will not use certificates. I'm using the
sample code "mkit" to accomplish self certification.
I do need public/private keys however, and I need the "server" to encrypt
the public key before sending it out. This does not seem to be something
the designers intend the co
signed up, but did not get confirm on the user list, only announce.
Testing ...
--
corky peavy
[EMAIL PROTECTED] - email
(512) 682-6934 x6527 - voicemail/fax
__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http
