tfpauly/privacy-proxy issues and pull requests

#49 - What stops a client from using a ton of mediators?

Issue - State: closed - Opened by tfpauly about 3 years ago - 3 comments
Labels: Private Access Tokens

#48 - Do we need mutual auth between Mediator and Issuer?

Issue - State: closed - Opened by tfpauly about 3 years ago - 3 comments
Labels: Private Access Tokens

#48 - Do we need mutual auth between Mediator and Issuer?

Issue - State: closed - Opened by tfpauly about 3 years ago - 3 comments
Labels: Private Access Tokens

#47 - Describe how to instantiate motivating use cases

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#47 - Describe how to instantiate motivating use cases

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#46 - Describe Issuer decryption steps

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#46 - Describe Issuer decryption steps

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#45 - Expand token security considerations

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#45 - Expand token security considerations

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#44 - Include Mediator's validation of keys in Security Considerations

Issue - State: closed - Opened by tfpauly about 3 years ago

#42 - Add motivating use cases

Pull Request - State: closed - Opened by janaiyengar about 3 years ago

#41 - Discuss related work, especially Privacy Pass

Issue - State: closed - Opened by janaiyengar about 3 years ago - 3 comments
Labels: Initial Version, Private Access Tokens

#40 - Add single issuer-mediator considerations

Pull Request - State: closed - Opened by smhendrickson about 3 years ago

#39 - First pass through Intro and Overview sections

Pull Request - State: closed - Opened by janaiyengar about 3 years ago - 1 comment

#38 - Clarify key discovery, remove OHTTP dependency

Pull Request - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#37 - Describe geolocation use case with per-geo keys

Issue - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#36 - Is the public key per issuer or per origin?

Issue - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#35 - Add protocol diagram for Private Access Tokens

Issue - State: closed - Opened by dvorak42 about 3 years ago
Labels: Initial Version, Private Access Tokens

#34 - Describe captcha/fraud rate limiting use case alongside metered paywalls

Issue - State: closed - Opened by tfpauly about 3 years ago - 2 comments

#33 - Look at replacing OHTTP with a single encrypted header

Issue - State: closed - Opened by tfpauly about 3 years ago

#32 - Make the PrivateAccessToken format stand-alone

Pull Request - State: closed - Opened by tfpauly about 3 years ago

#31 - Reconcile PrivateAccessToken and PrivacyToken schemes

Issue - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#30 - Update authors for Private Access Tokens.

Pull Request - State: closed - Opened by dvorak42 about 3 years ago

#29 - Make PATs interactive.

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#28 - Add Scott/Steven to authors

Issue - State: closed - Opened by tfpauly about 3 years ago - 1 comment

#27 - Discuss Trust Token relations

Issue - State: closed - Opened by chris-wood about 3 years ago - 1 comment

#26 - First party set support?

Issue - State: closed - Opened by smhendrickson about 3 years ago - 1 comment
Labels: Future Version, Private Access Tokens

#25 - Describe how origins specify which issuer to use

Issue - State: closed - Opened by tfpauly about 3 years ago - 3 comments

#24 - Clarify single mediator-issuer requirements

Issue - State: closed - Opened by smhendrickson about 3 years ago

#23 - Discuss token scoping

Issue - State: closed - Opened by smhendrickson about 3 years ago - 2 comments

#22 - Discuss fallback options

Issue - State: closed - Opened by smhendrickson about 3 years ago - 2 comments
Labels: Private Access Tokens

#21 - Redemption binding to requests

Issue - State: closed - Opened by dvorak42 about 3 years ago - 1 comment

#20 - Private Access Tokens should have an interactive mode

Issue - State: closed - Opened by tfpauly about 3 years ago - 5 comments

#19 - Discuss TLS MITM for Private Access Tokens

Issue - State: closed - Opened by tfpauly about 3 years ago

#18 - Redeemer's Issuer Configuration

Issue - State: closed - Opened by dvorak42 about 3 years ago - 1 comment

#17 - Split up 'client re-identification' into two use cases

Pull Request - State: closed - Opened by smhendrickson about 3 years ago

#16 - Issuer and mediator can collude privately

Issue - State: closed - Opened by smhendrickson about 3 years ago - 2 comments
Labels: Private Access Tokens

#15 - First read nits

Pull Request - State: closed - Opened by smhendrickson about 3 years ago

#14 - Clarify that Private Access Tokens are bound to origins

Issue - State: closed - Opened by tfpauly about 3 years ago - 2 comments

#13 - Should we require multiple issuers per redeemer?

Issue - State: closed - Opened by tfpauly about 3 years ago - 2 comments

#12 - Add examples and more considerations.

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#11 - Add more derivation bits

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#10 - Shuffle things around, and add some color.

Pull Request - State: closed - Opened by chris-wood about 3 years ago

#9 - Significant changes for Proxy DNS and SVCB request/response handling : try 2

Pull Request - State: open - Opened by enygren over 3 years ago - 2 comments

#8 - Support alternate key lengths

Pull Request - State: closed - Opened by enygren over 3 years ago - 1 comment

#7 - Support both rsa2048 and rsa4096

Pull Request - State: closed - Opened by enygren over 3 years ago - 4 comments

#6 - Significant changes for Proxy DNS and SVCB request/response handling

Pull Request - State: closed - Opened by enygren over 3 years ago - 3 comments

#5 - Fix the RSA Blind Signature reference.

Pull Request - State: closed - Opened by chris-wood over 3 years ago

#4 - Strongly reference RSA blind in the Privacy Token Structure section

Issue - State: closed - Opened by tfpauly over 3 years ago

#3 - Expand KeyID, and clarify its format.

Pull Request - State: closed - Opened by chris-wood over 3 years ago - 6 comments

#2 - Expand key_id to 8 bytes

Issue - State: closed - Opened by enygren over 3 years ago - 3 comments

#1 - Allow privacy token to support either 2048 or 4096 RSA keys

Issue - State: closed - Opened by tfpauly over 3 years ago - 4 comments

GitHub / tfpauly/privacy-proxy issues and pull requests