- Original Message -
> From: "ianG"
> To: dev-tech-crypto@lists.mozilla.org
> Sent: Thursday, April 26, 2012 6:14:43 AM
> Subject: Re: Feedback on DOMCryptInternalAPI
>
> > I don't imagine we will have an address bound the the public key.
>
>
> In some countries e.g., in Europe, identi
> If you want the signature + document to be legally sustainable and/or
> user-interpretable, then plaintext signatures with embedded public keys are
> the way to go. You can base64-encode the public keys :) Some further
> development of this theme is at
> http://iang.org/papers/ricardian_contrac
(couple of off the wall observations, 'scuse the fast typing...)
On 26/04/12 01:53 AM, David Dahl wrote:
I have experienced some issues regarding to encoding.
A page encoded in ISO send some data to a page encoded in UTF-8 which
signs...then, verify could not match.
So we decide to use base64
> Supporting smart cards in the spec and first implementations is not a goal,
> however, I think a lot of the base work we are doing will help in a future
> iteration. For instance, I hope that this Gecko 'internal API' will help
> extension and browser developers to experiment with smartcards,
4 matches
Mail list logo
