ISSUE-9: what will be the mean to integrate in the API the fact that key usage may need user consent ?

user consent

what will be the mean to integrate in the API the fact that key usage may need user consent ?

State:

CLOSED

Product:

design for Web Crypto API

Raised by:

Virginie GALINDO

Opened on:

2012-08-01

Description:

During the F2F Summer meeting we all agreed that the user interface was not part of the API deliverable, nevertheless it is required to interact with the user when sensitive data are manipulated by an application. This issue is raised to keep track of the fact that we will need to have a mean to integrate this warning within our specification.

Related Actions Items:

No related actions

Related emails:

1. [minutes] Re: W3C Web Crypto WG - monday 4th of march (from wseltzer@w3.org on 2013-03-04)
2. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
3. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
4. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
5. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
6. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from rbarnes@bbn.com on 2013-03-04)
7. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from watsonm@netflix.com on 2013-03-04)
8. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
9. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from rbarnes@bbn.com on 2013-03-04)
10. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
11. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
12. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
13. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
14. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
15. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from sleevi@google.com on 2013-03-04)
16. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
17. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from watsonm@netflix.com on 2013-03-04)
18. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
19. Re: ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from watsonm@netflix.com on 2013-03-04)
20. RE: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from Virginie.GALINDO@gemalto.com on 2013-03-04)
21. Re: W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from hhalpin@w3.org on 2013-03-04)
22. ISSUE-9 [was Re: ISSUE-30: Key import/export?] (from hhalpin@w3.org on 2013-03-04)
23. W3C Web Crypto WG - agenda for our call on monday 4th of march @ 20:00 UTC (today) (from Virginie.GALINDO@gemalto.com on 2013-03-04)
24. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from watsonm@netflix.com on 2013-02-04)
25. RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Asad.Ali@gemalto.com on 2013-02-04)
26. Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from S.Durbha@cablelabs.com on 2013-02-04)
27. W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-02-04)
28. PROPOSAL: Close ISSUE-9 (from sleevi@google.com on 2013-01-31)
29. crypto-ISSUE-9 (user consent): what will be the mean to integrate in the API the fact that key usage may need user consent ? [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-01)

Related notes:

No additional notes.

Display change log