- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Dec 2014 03:35:36 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27564 Bug ID: 27564 Summary: Must conforming implementations match the order of errors? Product: Web Cryptography Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Web Cryptography API Document Assignee: sleevi@google.com Reporter: ericroman@google.com CC: public-webcrypto@w3.org My interpretation of section "3. Conformance" is that yes, the order of errors must match that enumerated by the spec's pseudo-code. I would like to relax this requirement since some of the error orders given by the spec restrict implementations. For instance: * Empty usages is tested _after_ having generated/imported a key. However it would make more sense for an implementation to test for this error before creating the key (also faster failure for caller) * Usage testing when unwrapping a key is done after decryption (as part of importKey). Whereas implementations could rejected invalid usages (in many cases) sooner before doing the decryption. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 11 December 2014 03:35:37 UTC