Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / tfpauly/privacy-proxy issues and pull requests

#102 - Add binding details to security considerations

Issue - State: closed - Opened by chris-wood almost 3 years ago - 1 comment
Labels: Private Access Tokens

#101 - NIZK security properties

Issue - State: closed - Opened by chris-wood almost 3 years ago
Labels: Private Access Tokens

#101 - NIZK security properties

Issue - State: closed - Opened by chris-wood almost 3 years ago
Labels: Private Access Tokens

#100 - Check origin_name

Issue - State: closed - Opened by chris-wood almost 3 years ago - 5 comments
Labels: Private Access Tokens

#100 - Check origin_name

Issue - State: closed - Opened by chris-wood almost 3 years ago - 5 comments
Labels: Private Access Tokens

#99 - Rename name_key_id to issuer_key_id

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

#99 - Rename name_key_id to issuer_key_id

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

#98 - Mention how ISSUER_NAME is used

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

#98 - Mention how ISSUER_NAME is used

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

#97 - Multiple layers of privacy-proxy.

Issue - State: open - Opened by jhoyla about 3 years ago

#97 - Multiple layers of privacy-proxy.

Issue - State: open - Opened by jhoyla about 3 years ago

#96 - Groth-Sahai based alternative?

Issue - State: open - Opened by wbl about 3 years ago - 4 comments

#96 - Groth-Sahai based alternative?

Issue - State: open - Opened by wbl about 3 years ago - 4 comments

#95 - Explain multiple challenges

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

#95 - Explain multiple challenges

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

#94 - batched tokens

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

#94 - batched tokens

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

#93 - Align parameter configuration with best practices (ACME)

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

#93 - Align parameter configuration with best practices (ACME)

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

#92 - Reference collusion risks earlier in document

Pull Request - State: closed - Opened by tfpauly about 3 years ago - 1 comment
Labels: Private Access Tokens

#92 - Reference collusion risks earlier in document

Pull Request - State: closed - Opened by tfpauly about 3 years ago - 1 comment
Labels: Private Access Tokens

#91 - note mediator/origin timestamp collusion

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

#91 - note mediator/origin timestamp collusion

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

#90 - Add privacy pass reference

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

#90 - Add privacy pass reference

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

#89 - Client state loss

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

#89 - Client state loss

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

#88 - Fix typos in draft-private-access-tokens.md

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

#88 - Fix typos in draft-private-access-tokens.md

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

#87 - CLIENT_ID -> CLIENT_KEY

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

#87 - CLIENT_ID -> CLIENT_KEY

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

#86 - Some structural changes to the protocol section

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

#86 - Some structural changes to the protocol section

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

#85 - Clarify requirements around endpoint auth

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

#85 - Clarify requirements around endpoint auth

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

#84 - Fix long line

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

#84 - Fix long line

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

#83 - Add section on Client identity

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

#82 - Adds architecture section

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

#82 - Adds architecture section

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

#81 - Merge pull request #79 from tfpauly/smhendrickson-patch-2

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

#80 - Dependency pointers and implementation requirement clarification

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

#80 - Dependency pointers and implementation requirement clarification

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

#79 - ORIGIN_TOKEN_KEY rotation deployment info

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

#79 - ORIGIN_TOKEN_KEY rotation deployment info

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

#78 - Discuss the privacy implications of client policy around Sec-CH-Geohash

Issue - State: closed - Opened by jyasskin about 3 years ago - 2 comments
Labels: Geo Hint

#78 - Discuss the privacy implications of client policy around Sec-CH-Geohash

Issue - State: closed - Opened by jyasskin about 3 years ago - 2 comments
Labels: Geo Hint

#77 - Normatively define the mapping from lat/lon to/from Sec-CH-Geohash

Issue - State: closed - Opened by jyasskin about 3 years ago - 2 comments
Labels: Geo Hint

#77 - Normatively define the mapping from lat/lon to/from Sec-CH-Geohash

Issue - State: closed - Opened by jyasskin about 3 years ago - 2 comments
Labels: Geo Hint

#76 - Token key ID and rotation

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

#76 - Token key ID and rotation

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

#75 - Clarify client guardrails for tracking

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

#74 - Add discussion of tracking using client token state.

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

#74 - Add discussion of tracking using client token state.

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

#73 - Describe user interaction guidelines

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

#73 - Describe user interaction guidelines

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

#72 - Formalize HTTP headers

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

#72 - Formalize HTTP headers

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

#71 - Add cryptographic dependencies section

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

#71 - Add cryptographic dependencies section

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

#70 - Discuss client identity

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

#70 - Discuss client identity

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

#69 - Discuss clients losing state

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

#69 - Discuss clients losing state

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

#68 - Second pass at protocol rework

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

#68 - Second pass at protocol rework

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

#67 - Token-Count tracking

Issue - State: closed - Opened by chris-wood about 3 years ago - 2 comments
Labels: Initial Version

#67 - Token-Count tracking

Issue - State: closed - Opened by chris-wood about 3 years ago - 2 comments
Labels: Initial Version

#66 - Describe Issuer validation of client groups

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

#66 - Describe Issuer validation of client groups

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

#65 - Describe user interaction

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

#65 - Describe user interaction

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

#64 - Define HTTP headers as structured fields

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

#64 - Define HTTP headers as structured fields

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

#63 - Private Access Token protocol rework

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

#63 - Private Access Token protocol rework

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

#62 - Nits and fix

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

#62 - Nits and fix

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

#61 - Adding self to draft

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

#61 - Adding self to draft

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

#60 - Add Jana to authors on Private Access Tokens

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

#60 - Add Jana to authors on Private Access Tokens

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

#59 - anon_origin_id is visible to Issuer

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

#59 - anon_origin_id is visible to Issuer

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

#58 - ANON_ORIGIN_ID_PRIME example doesn't work

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

#58 - ANON_ORIGIN_ID_PRIME example doesn't work

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

#57 - Issuer key rotation

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

#57 - Issuer key rotation

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

#55 - Prevent clients from changing their ANON_CLIENT_ID

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

#54 - Describe mediator policy about talking to issuers

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

#54 - Describe mediator policy about talking to issuers

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

#53 - Make token keys per-origin

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

#53 - Make token keys per-origin

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

#51 - Binding between ORIGIN_ID and token request

Issue - State: closed - Opened by chris-wood about 3 years ago - 4 comments

#51 - Binding between ORIGIN_ID and token request

Issue - State: closed - Opened by chris-wood about 3 years ago - 4 comments

#50 - geo-location use case

Issue - State: open - Opened by janaiyengar about 3 years ago - 2 comments
Labels: Future Version, Private Access Tokens

#50 - geo-location use case

Issue - State: open - Opened by janaiyengar about 3 years ago - 2 comments
Labels: Future Version, Private Access Tokens

#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