- From: Ryan Sleevi <sleevi@google.com>
- Date: Thu, 4 Apr 2013 16:37:07 -0700
- To: Lu HongQian Karen <karen.lu@gemalto.com>
- Cc: Mark Watson <watsonm@netflix.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Hutchinson Michael <Michael.Hutchinson@gemalto.com>
Issuer is underspecified, and as such, not possible to implement.
Further, this seems to directly conflict with the charter, which states:
"Out of scope: features including special handling directly for
non-opaque key identification schemes, access-control mechanisms
beyond the enforcement of the same-origin policy, and functions in the
API that require smartcard or other device-specific behavior"
This requires both handling for non-opaque key identification scheme
("issuer") as well as an access control mechanism ("isPrivate")
As such, we do not support the WG taking on this item.
On Thu, Apr 4, 2013 at 4:21 PM, Lu HongQian Karen <karen.lu@gemalto.com> wrote:
> Hi Mark,
>
> We would like to suggest expanding the key discovery specification by adding an API for discovering pre-provisioned cryptographic keys via any of their attributes. This gives web applications a mean to find pre-provisioned keys whose names are unknown to them.
>
> The contribution is attached for review.
>
> Regards,
> Karen and Michael
>
>
Received on Thursday, 4 April 2013 23:37:33 UTC