W3C home > Mailing lists > Public > public-webcrypto@w3.org > July 2014

[Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Jul 2014 02:36:12 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-26465-7213-3oNcJudp7G@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26465

--- Comment #2 from Mark Watson <watsonm@netflix.com> ---
(In reply to Ryan Sleevi from comment #1)
> Mark,
> 
> I've read through this bug several times, and your other comment, and it's
> still entirely opaque to me what you see the problem as, nor what you're
> proposing as the solution.

I thought what I said was pretty clear. I'll write a reply to my own post with
additional clarification.

> 
> Your comment about (type, DOMString?) makes me think you're wanting to
> introduce a new interface, which surely doesn't sound right. The nullability
> of DOMString? alone raises concerns.

No, I didn't say anything about an interface.

> 
> Perhaps you could try restating the problem as you see it.
> 
> If you're objecting to the specialization of HashAlgorithmIdentifier, well,
> another solution is to simply allow digest algorithms to be used for all
> operations, since they are 'leaves' (if I understand what you're referring
> to) in nearly all supported operations.
> 
> Still, clarity desired.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 30 July 2014 02:36:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:23 UTC