- From: Harry Halpin <hhalpin@w3.org>
- Date: Fri, 25 Nov 2011 10:47:09 +0100
- To: Brian Smith <bsmith@mozilla.com>
- CC: public-identity@w3.org
On 11/25/2011 03:42 AM, Brian Smith wrote:
> Harry Halpin wrote:
>> 1) To determine if device is suitable for certain content
>> 2) Loading keys from a USB/smartcard for financial transactions
>> ("Korean bank" use-case)
>> 3) Identity claims signing
>> 4) JS Code-signing
>> 5) Helping OAuth
> It would also be useful to know the necessary and sufficient features for each use case.
Agree - that's why I'm now adding the people who suggested each use-case :)
1) To determine if device is suitable for certain content (Mark)
2) Loading keys from a USB/smartcard for financial transactions
("Korean bank" use-case) (Channy/Virginie/Anders)
3) Identity claims signing (Ben)
4) JS Code-signing (Tobie)
5) Helping OAuth (Jeff)
I'm also trying to figure out if there's more use-cases with their own
necessary and sufficient features. I'd assume so, but need people to
make this known over the mailing list.
> I believe some people expect to be able to create pure-JS S/MIME-like and/or PGP-like message privacy features, that have some useful security benefit over giving the keys to the messaging provider to store/use on its server, even though the email provider would deliver the JS that would use the crypto primitives to implement those privacy features.
>
> - Brian
Received on Friday, 25 November 2011 09:46:59 UTC