Ecosyste.ms: Issues

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

GitHub / shivankaul/star-spec issues and pull requests

#43 - Consider batching all reports at the proxy

Issue - State: open - Opened by bemasc almost 2 years ago - 9 comments

#42 - Change controller for media types: IESG => IETF

Pull Request - State: open - Opened by ShivanKaul almost 2 years ago

#41 - Describe attack where AS can detect presence of specific measurements

Pull Request - State: closed - Opened by ShivanKaul about 2 years ago

#40 - Experimental status

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

#39 - Adopt TSS draft

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

#38 - Miscellaneous fixes

Pull Request - State: closed - Opened by ShivanKaul over 2 years ago

#37 - Merge share and commitment into a single structure

Issue - State: open - Opened by chris-wood over 2 years ago

#36 - IANA considerations

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

#35 - Add IANA considerations for new media types

Issue - State: closed - Opened by chris-wood over 2 years ago

#34 - Specify Feldman's VSS scheme

Pull Request - State: closed - Opened by chris-wood over 2 years ago - 1 comment

#32 - Add discussion about "garbage reports"

Issue - State: closed - Opened by chris-wood over 2 years ago

#31 - Specify verifiable secret sharing

Issue - State: closed - Opened by chris-wood over 2 years ago

#30 - Make commitments a part of the secret sharing syntax

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

#29 - Use a VOPRF

Pull Request - State: closed - Opened by chris-wood over 2 years ago - 1 comment

#28 - Frame the report_data plaintext so it can be parsed

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

#27 - Corrupt reports

Issue - State: open - Opened by martinthomson over 2 years ago - 3 comments

#26 - Fix block styling

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

#25 - Specify secret-sharing scheme

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#24 - Refactor the spec

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

#23 - What information is leaked through common tags?

Issue - State: open - Opened by ShivanKaul over 2 years ago - 1 comment

#22 - Garbage reports

Issue - State: open - Opened by ShivanKaul over 2 years ago - 2 comments

#21 - Use key-committing AEAD for the message encryption

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment

#20 - Hardcode a specific modulus for Shamir scheme

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment

#19 - Use traditional Shamir Secret Sharing instead of Adept

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

#18 - Clarify consequences of single aggregation server

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#17 - Adds details to dictionary attacks based on leakage

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#16 - Be more prescriptive about OHTTP usage.

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#15 - Update System Architecture diagram to include randomness server

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment

#14 - Add more details on leakage

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#13 - Add auxiliary data clarification and comparison

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#13 - Add auxiliary data clarification and comparison

Pull Request - State: closed - Opened by alxdavids over 2 years ago

#12 - Add text that states VOPRFs can be used

Pull Request - State: closed - Opened by alxdavids over 2 years ago - 1 comment

#11 - Collusion risk

Issue - State: closed - Opened by ShivanKaul over 2 years ago
Labels: clarify

#10 - Requires only one server in aggregation phase

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment
Labels: comparison

#9 - Clients can send auxiliary info

Issue - State: closed - Opened by ShivanKaul over 2 years ago
Labels: clarify, comparison

#8 - STAR leaks the fact that 2 encrypted measurements are the same

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment
Labels: clarify, comparison

#7 - Remove use of "puncturable" POPRFs from the draft

Issue - State: closed - Opened by ShivanKaul over 2 years ago

#5 - Clarify what we mean by "randomness"

Issue - State: closed - Opened by ShivanKaul over 2 years ago

#4 - Clarify what aux data is and how it's used

Issue - State: closed - Opened by ShivanKaul over 2 years ago

#3 - Compare security guarantees with Poplar

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 1 comment

#2 - Only use "regular" STAR, move STARlite to a new optional section

Issue - State: closed - Opened by ShivanKaul over 2 years ago - 2 comments

#1 - Be prescriptive about use of oblivious HTTP

Issue - State: closed - Opened by ShivanKaul over 2 years ago