Emmanuel Dreyfus wrote:
On Wed, Mar 17, 2010 at 11:24:37AM +0100, Anders Rundgren wrote:
I don't see much value supporting a function that still misses
the core question: is the key actually in the card?
I do not understand your concern. As far as I understand, the purpose
of popChallengeResponse is to prove you have the private key for a
given public key.
That's correct. But even if you send a stolen static cert req, you don't
get very far with that since if you haven't the private key you can't
use the returned cert anyway which I guess is why this function haven't been
much requested.
I'm not sure what you had intended to use this function for but my rant
about the core question is related: if you do local key generation and
cannot in some way vouch for the key storage, the security level of the
system is below that of a smart card to take an example.
Currently the issuer can't even ask you to protect keys with PIN-codes
so I would suggest doing nothing or doing it right.
I'm personally quite leary about exposing more crypto in JavaScript, you pretty
soon endup in a very dark corner. Using a well-defined XML protocol often
means that you can do all crypto from trusted middleware.
Anders
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
