Git-Mirrors/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2025-09-21 05:24:46 -04:00
Code Issues Projects Releases Packages Wiki Activity

add clarification on private access tokens vs privacy pass

Browse source
This commit is contained in:
fria 2025-03-30 19:12:17 -05:00 • committed by GitHub
parent a16cb75677
commit 849038880d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
blog/posts/privacy-pass.md
View file

@ -156,7 +156,7 @@ A browser-level API, I imagine, would significantly reduce the development burde
[Private Access Tokens](https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/) are based on Privacy Pass as well, but they don't seem to be specifically bound to the browser.
It's unclear to me what really makes Private Access Tokens different than Privacy Pass itself, other than Private Access Tokens seem to require separation of the Attester and Issuer while Privacy Pass doesn't, which adds extra privacy.
It's unclear to me what really makes Private Access Tokens different than Privacy Pass itself, other than Private Access Tokens seem to call for separation of the Attester and Issuer while Privacy Pass allows the origin, attester, and issuer to be the same. Delegating each role to a different party adds extra privacy.
The origin website only knows your URL and IP from the initial connection.