Re: RFC7512 PKCS#11 URI support

Ryan Sleevi <[email protected]>
Newsgroups gmane.comp.mozilla.crypto
Message-ID <CAErg=HHCAckLT5iFVkFdotX2onXBqHq_BfuYJp7qTX_mYqEo7g@mail.gmail.com>
On Mon, Apr 4, 2016 at 3:45 PM, David Woodhouse <[email protected]> wrote:
> That won't change. Unless you explicitly use a new function that
> provides a URI instead of a nickname, of course.
>
> You will *only* get a URI from direct user input, in a situation where
> a user could already feed you any kind of nonsense.

And if you try to filter out that non-sense - for example, relying on
that format - you end up with bad results. If you try to act upon that
user data, on the assumption it follows the format - you end up with
bad results.

I appreciate your argument "but user provided!", but you seem to be
missing the core point - you're changing the syntax of an API's
arguments, in a way that breaks the previously-held pre and post
conditions. That's an API change.

If we can't agree on that, then it's no surprise that you don't agree
with or appreciate the objections, but I'm not sure what more can be
said, or needs to be said. It seems we've reached an ideological
impasse.
-- 
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.