Using a password as a private key.
Christopher Steel - Java Design Center McLean VA
Chris.Steel at East.Sun.COM
Tue Oct 27 15:44:12 PST 1998
Why not encrypt the private key with a 128 bit symmetric key (created from the hash of a username and paasword)
and store on a keyserver, along with the public key?
That way, you don't have to store it yourself locally, you get it off the keyserver.
I wrote a keyserver that does just that. In addition, it also verifies ies the user before returning the key.
It requires the user to encrypt a known string with a separate password.
The encrypted string is sent to the keyserver, encrypted with the keyserver's public key.
Seems rather safe. Anyone disagree?
-Chris
P.S. I might not use it for military purposes, but for company email...
"RedRook" <redrook at yahoo.com> wrote:
>Date: Tue, 27 Oct 1998 13:53:07 -0800 (PST)
>Assymetic crypto systems such as
>Diffie-Hellman, El-Gamel, and DSS, allow the private key to be a
>randomly chosen number. But, as a cute hack, instead of using a
>random number, for the private key, you could use a hash of the User
>Name, and a password.
>
>Doing so allows the users to generate their private key on demand.
>They don't have to store the private key, and if they want to work on
>a another computer, they don't need to bring along a copy.
>Has any one tried this? Is there existing software that does this? Any
>comments on the security of such a scheme?
>The only draw back that I can think of is the potential lack of
>randomness in the key. If the user chooses a bad password, it would be
>possible to brute force the public key.
>Harv.RedRook at yahoo.com
>_________________________________________________________
>DO YOU YAHOO!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
More information about the cypherpunks-legacy
mailing list