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 Web Cryptography Working Group Issue Tracker on 2012-08-01 (public-webcrypto@w3.org from August 2012)

From: Web Cryptography Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 01 Aug 2012 16:00:07 +0000
To: public-webcrypto@w3.org
Message-Id: <E1SwbLD-0003PW-9h@tibor.w3.org>

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]

http://www.w3.org/2012/webcrypto/track/issues/9

Raised by: Virginie GALINDO
On product: Web Cryptography API

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.

Received on Wednesday, 1 August 2012 16:00:12 UTC