- From: Harry Halpin <hhalpin@w3.org>
- Date: Fri, 21 Nov 2014 02:42:51 +0100
- To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Also, to move to CR we really should close two dangling references in the spec to ISSUE-35, which we closed back in February: See resolution for closure here: https://www.w3.org/2012/webcrypto/track/issues/35 The two references are: 1) In Section 14, the reference to // TBD: ISSUE-35 2) And following Editorial Note: "ISSUE-35: The specification for wrapKey/unwrapKey does not specify how authors that do not trust the execution environment may indicate required attributes for keys that are unwrapped. An example is unwrapping a key with a non-extractable key, marking the newly unwrapped key as non extractable, and then further indicating that all keys unwrapped with the newly unwrapped key are also non-extractable." If folks want to keep that as an informative note, that's fine - just remove the references to "TBD: ISSUE 35" and change text so that it doesn't appear the issue is still open in the spec text. These are likely to block CR transition at W3C review and cause confusion in readers about whether wrapping/unwrapping might change, so it would be great if an editor would fix them. My understanding is basically, in a non-"trusted execution environment", we can't enforce parameters. A number of other editorial notes that seem to signal unresolved problems (even if WG has resolved problem) were mentioned in my previous email and Bugzilla. Can one of the editors give these a look and make the needed edits as soon as they can? cheers, harry
Received on Friday, 21 November 2014 01:43:04 UTC