W3C home > Mailing lists > Public > public-webcrypto@w3.org > January 2015

[Bug 27603] verify() can fail either by returning flase or rejecting with an error, inconsistent which is used

From: <bugzilla@jessica.w3.org>
Date: Mon, 05 Jan 2015 18:08:10 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-27603-7213-Wbu87hHAC3@http.www.w3.org/Bugs/Public/>

Mark Watson <watsonm@netflix.com> changed:

           What    |Removed                     |Added
                 CC|                            |watsonm@netflix.com

--- Comment #1 from Mark Watson <watsonm@netflix.com> ---
The original intention was that 'false' is used for cases where all the
parameters are valid, the cryptographic operations succeed, but the final
signature value just doesn't match the one provided. Other cases would be an

We should resolve this in favor of what libraries provide. If there is an
example library which does not expose the distinction then I guess we should
move them all to errors.

If the distinction is generally available, then we need to make the
specification consistent with the original intention.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 5 January 2015 18:08:12 UTC

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