Re:Authentication and the Have I Been Pwned API
by diminoten on Monday July 22, 2019 @02:47PM
(#20501015)
You don't get to take issue with any of this. Your information was already stolen! You have no say, the end.
Re:Authentication and the Have I Been Pwned API
by jtbayly on Monday July 22, 2019 @03:11PM
(#20501272)
So your fallback position is that it is perfectly legitimate to traffic in stolen PII. Got it.
Well, I take issue with that.
Re:Authentication and the Have I Been Pwned API
by diminoten on Wednesday July 24, 2019 @12:16AM
(#20512330)
Yes, in some cases it's perfectly legitimate to "traffic" (terrible word choice) in stolen PII, that is correct.
And my "fallback" position is that it's better this way than the other way, where it's actually being trafficked, rather than your hyperbolic assertion that it is now.
This is software acting as an agent of the effected user. 1Password could be authorized by the email holder to gain access to the API without making the information public.
> Other websites won't allow you to use...
This and the following example in your comment are discussing the breached password API, which is a completely different API that I specifically mentioned up-front as not compromising any PII.
I take zero issue with providing an API to see counts of how many times a password has shown up on breach lists, although I wouldn't use the API myself on any of my own passwords, because it leaks a 1-in-1-million discriminator to the actual password you are querying.