Re:Replace CAPTCHAs with Private Access Tokens
by pmoriarty on Monday June 20, 2022 @09:08PM
(#31818502)
Then I guess its widespread adoption is inevitable, because if there's one thing corporations seem to be incapable of resisting is a more effective way of tracking people.
Re:Replace CAPTCHAs with Private Access Tokens
by Dylan16807 on Tuesday June 21, 2022 @02:10PM
(#31827162)
The cryptography says tracking a token is not possible. So would you like to elaborate on that point?
I see you made a different comment about correlating connections but you can get a bunch of tokens at once and slowly go through the pile over several hours, as far as I know.
Re:Replace CAPTCHAs with Private Access Tokens
by Dylan16807 on Tuesday June 21, 2022 @02:53PM
(#31827625)
Basically, the client picks some numbers, gets one derivative of those numbers signed, and presents a different derivative of its numbers to be verified.
With the right math, there's no way to connect the two transactions.
>The website knows only your URL and IP, which it has to know to make a connection.
>The device manufacturer (attester) knows only the device data required to attest your device, but can't tell what website you visited, and doesn’t know your IP.
>Cloudflare knows the site you visited, but doesn’t know any of your device or interaction information.
Re:Replace CAPTCHAs with Private Access Tokens
by feet on Tuesday June 21, 2022 @02:04PM
(#31827105)
With how much data cloudflare has access to and how the market for data is, I don't believe it for a second that they can't correlate connections even if what you say is true
Re:Replace CAPTCHAs with Private Access Tokens
by remram on Monday June 20, 2022 @11:45PM
(#31819599)
In what situation does a proof-I-have-a-free-account (token) replace a proof-a-human-initiated-this-action (captcha)? Don't they have completely unrelated goals?
Re:Replace CAPTCHAs with Private Access Tokens
by badrabbit on Monday June 20, 2022 @09:01PM
(#31818442)
mTLS and apple/google/other-idp signed short-lived client certs would acheive the same thing in my opinion. Bypass captcha if the client has a cert issued by a trusted idp.
I see you made a different comment about correlating connections but you can get a bunch of tokens at once and slowly go through the pile over several hours, as far as I know.
With the right math, there's no way to connect the two transactions.
https://www.ietf.org/id/draft-ietf-privacypass-protocol-04.h...
https://privacypass.github.io/protocol/
>The website knows only your URL and IP, which it has to know to make a connection.
>The device manufacturer (attester) knows only the device data required to attest your device, but can't tell what website you visited, and doesn’t know your IP.
>Cloudflare knows the site you visited, but doesn’t know any of your device or interaction information.
Privacy Pass: Protocol Design Explanation
https://news.ycombinator.com/item?id=31818700