- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Jul 2014 01:23:32 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26465 Bug ID: 26465 Summary: Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields Product: Web Cryptography Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Web Cryptography API Document Assignee: sleevi@google.com Reporter: watsonm@netflix.com CC: public-webcrypto@w3.org Our algorithm normalization rules assume that the target Dictionary type is dependent on the ( algorithm name, operation ) pair. Algorithm normalization is invoked recursively for member entries of AlgorithmIdentifier type. The name to be used is just the value specified in the input data, but the operation is "hard-coded" in the specification as follows: - if the type is HashAlgorithmIdentifier, then "digest" - otherwise, use the same value as the outer normalization This seems restrictive. I suggest that the "leaf" values in the [[supportedAlgorithms]] structure be changed from just a type to a ( type, DOMString? ) pair, with the rule that the DOMString must be non-null if and only if the type is or is derived from AlgorithmIdentifier. Then this would be the operation used for recursive invokation of algorithm normalization. The 'define an algorithm' procedure and the invokations of it would need amending as well. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 30 July 2014 01:23:33 UTC