Re: [TLS] User Defined Key Pair

["OMAR HASSAN (RIT Student)" <[e-mail]>]

Hi Rich,

The idea is to separate the generation of the key pair of the server, so
the server will be expecting your public key during the enrollment, and a
message singed by your private key during the sign in.

On the browser level there should be a plugin that has a function to
generate the key pair, that function must generate the same key pair for
the same input parameters.

I didn't include any mathematics details for that function as I was
interesting in abstracting the idea, and for the real implementation there
must be unified implementation across all browsers to generate the same key
pair for the same input parameters in all browsers.

There should be three version of the generate key function as the following:

1) genKeyPair (username, password, security question&answer);
So whenever you provide the same username, password, and the security
question&answer, the same key pair will be generated for you.

2) genKeyPair (username, password, file);
So whenever you provide the same username, password, and the same file from
a usb or hard drive, the same key pair will be generated for you.

3) genKeyPair (username, password, smart card or hardware token);
So whenever you plugin the hardware token or put your smart card, and
provide the same username and password, the same key pair will be generated
for you.

In my prof of concept implementation, I used a standard java method that
will generate the same key pair for the same input string, and I provided a
concatenation of the username, password, and security question&answer.


On Mon, Jun 24, 2013 at 6:29 PM, Salz, Rich <[e-mail]> wrote:

> I didn’t see any description of your genKeyPair function; is it described
> anywhere?  In particular, it seems to me that it’s stateless – that is, it
> generates the keypair whenever needed, based only on the username,
> password, and a security question&answer.  Is that true?****
>
>                 /r$****
>
> ** **
>
> --  ****
>
> Principal Security Engineer****
>
> Akamai Technology****
>
> Cambridge, MA****
>
> ** **
>