DP-3T/documents issues and pull requests

#100 - Deanonimization of reported users

Issue - State: open - Opened by vaudenay over 4 years ago - 3 comments
Labels: privacy risk

#99 - replay/relay attacks for false alert injection

Issue - State: open - Opened by vaudenay over 4 years ago - 9 comments
Labels: protocol

#98 - Design 2 - is there a truncate missing

Issue - State: closed - Opened by dirkx over 4 years ago - 1 comment
Labels: protocol

#97 - MAUP, spatial autocorrelation, and Context-Specificity of Contact data

Issue - State: open - Opened by BierJess over 4 years ago
Labels: usecases

#96 - Use HKDF-Expand instead of PRG and PRF?

Issue - State: closed - Opened by blipp over 4 years ago - 2 comments
Labels: protocol

#95 - Consent & Opt-in re: decision-making at the time of diagnosis and disadvantaged social groups

Issue - State: open - Opened by BierJess over 4 years ago - 2 comments
Labels: usecases

#94 - Trust in backend and HA to be seperate

Issue - State: open - Opened by jorants over 4 years ago - 1 comment
Labels: privacy risk, clarification

#93 - Design 2 - loose ends in the white paper / tighten up the spec

Issue - State: closed - Opened by dirkx over 4 years ago - 6 comments
Labels: protocol, clarification

#92 - Frame as adressing potential GDPR concerns

Issue - State: closed - Opened by BierJess over 4 years ago - 2 comments
Labels: legal

#91 - Explanation (explainability?) of app behaviour to the use

Issue - State: closed - Opened by davidbarnardwills over 4 years ago - 2 comments
Labels: app, clarification

#90 - Practical - are health authorities able to issue the authorization codes, right now?

Issue - State: closed - Opened by davidbarnardwills over 4 years ago - 8 comments
Labels: question, will-close-soon-without-further-input

#89 - Motion detection to modulate tx power

Issue - State: closed - Opened by inaitana over 4 years ago - 1 comment
Labels: bluetooth, usecases, will-close-soon-without-further-input

#88 - Clarify roaming behavior

Issue - State: closed - Opened by kugelfish42 over 4 years ago - 2 comments
Labels: clarification

#87 - Impractical suggestion for mitigating the main attacks

Issue - State: open - Opened by colmmacc over 4 years ago - 5 comments
Labels: protocol

#86 - Allow users in high risk state to publish their SK (notify contacts of contacts)

Issue - State: closed - Opened by diedicar over 4 years ago - 1 comment
Labels: app, usecases, will-close-soon-without-further-input

#85 - allow to prove that one is in high risk state without linking to the infected sk

Issue - State: closed - Opened by diedicar over 4 years ago - 11 comments
Labels: protocol, usecases, will-close-soon-without-further-input

#84 - Add mutations indicator to sent SK in case of infection.

Issue - State: closed - Opened by kkoenen over 4 years ago - 1 comment
Labels: protocol, usecases

#83 - Blockchain as decentralised storage?

Issue - State: closed - Opened by szetaa over 4 years ago - 11 comments
Labels: question, will-close-soon-without-further-input

#82 - Editable version of the documents

Pull Request - State: closed - Opened by dirkx over 4 years ago - 1 comment

#81 - TEE on the backend for better privacy (if the TEE is private).

Issue - State: closed - Opened by LefKok over 4 years ago - 1 comment
Labels: protocol

#80 - Epoch synchronization

Issue - State: open - Opened by defeo over 4 years ago - 8 comments

#79 - Clarification: sharing data with epidemiologists

Issue - State: open - Opened by pdehaye over 4 years ago - 1 comment

#78 - Malicious (modifying) backend could possibly easily create fake risk events(?)

Issue - State: closed - Opened by sk13 over 4 years ago - 1 comment
Labels: clarification, will-close-soon-without-further-input

#77 - TRUNCATE128 missing on p13

Issue - State: closed - Opened by defeo over 4 years ago - 6 comments
Labels: protocol

#76 - Excretion period starts n days before first symptoms

Issue - State: closed - Opened by alixMougenot over 4 years ago - 2 comments
Labels: protocol, usecases

#75 - Client Side Computation vs Bandwidth Considerations

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

#74 - Beacon info relaying (Denial of service)

Issue - State: closed - Opened by jorants over 4 years ago - 3 comments
Labels: question, privacy risk, will-close-soon-without-further-input

#73 - Bluetooth Distance assumption

Issue - State: closed - Opened by noci2012 over 4 years ago - 3 comments
Labels: bluetooth, clarification, will-close-soon-without-further-input

#72 - What is the security level of PRG( PRF( SKt, "broadcast key") )?

Issue - State: closed - Opened by tree-go over 4 years ago - 2 comments
Labels: protocol, clarification

#71 - Better/solidly define the Eph_id generator

Issue - State: closed - Opened by dirkx over 4 years ago - 3 comments
Labels: protocol

#70 - Traffic Light Syndrome

Issue - State: closed - Opened by mrseeker over 4 years ago - 6 comments
Labels: legal, privacy risk, will-close-soon-without-further-input

#69 - How to prevent preexisting Bluetooth tracking

Issue - State: open - Opened by noci2012 over 4 years ago - 41 comments
Labels: privacy risk, pinned

#68 - Describe interoperability strategy and certification

Issue - State: open - Opened by kugelfish42 over 4 years ago - 3 comments
Labels: documentation, protocol, suggested extension

#67 - Deanonymizing EphID handling

Issue - State: closed - Opened by kreativmonkey over 4 years ago - 1 comment
Labels: privacy risk, will-close-soon-without-further-input

#66 - Protect infected users against Bluetooth monitoring: ECDH key exchange

Issue - State: open - Opened by a8x9 over 4 years ago - 27 comments
Labels: protocol, suggested extension

#65 - Jumping LatLon

Issue - State: closed - Opened by obi458 over 4 years ago - 1 comment
Labels: protocol

#64 - The value for 'n' can be large

Issue - State: open - Opened by dirkx over 4 years ago - 4 comments
Labels: protocol

#63 - Securing the EphID store

Issue - State: open - Opened by dirkx over 4 years ago - 7 comments
Labels: protocol, suggested extension

#62 - Implementation: Test vectors

Issue - State: open - Opened by jaromil over 4 years ago - 43 comments
Labels: pinned

#61 - Increase the likelyhood that SK_t is shared by protecting the contacts of the person from involuntary disclorue

Issue - State: open - Opened by dirkx over 4 years ago - 2 comments
Labels: protocol, usecases, privacy risk, suggested extension

#60 - Proposal to ensure anonymity after infection

Issue - State: closed - Opened by leukipp over 4 years ago - 6 comments
Labels: protocol

#59 - Is just sharing contacts enough? better sharing contacts of contacts.

Issue - State: closed - Opened by diedicar over 4 years ago - 1 comment
Labels: question, usecases

#58 - Clarify how to ensure authenticity of Sks marked as infected

Issue - State: closed - Opened by kugelfish42 over 4 years ago - 2 comments
Labels: protocol, clarification, will-close-soon-without-further-input

#57 - Please clarify usage of AES in counter mode

Issue - State: closed - Opened by jaromil over 4 years ago - 8 comments
Labels: question, protocol

#56 - App on smartphones without SIM card

Issue - State: closed - Opened by FroehlichMarcel over 4 years ago - 1 comment
Labels: question, usecases

#55 - Clarify CDN usage

Issue - State: closed - Opened by jeffallen over 4 years ago - 1 comment
Labels: protocol, clarification

#54 - Public IPv4 addresses are not unique

Issue - State: closed - Opened by obi458 over 4 years ago - 4 comments
Labels: will-close-soon-without-further-input

#53 - Use GNUnet as decentaliced, anonymous data transport

Issue - State: closed - Opened by htgoebel over 4 years ago - 1 comment
Labels: protocol

#52 - Unclear statements about reporting of at-risk status to the health authority

Issue - State: closed - Opened by throwException over 4 years ago - 2 comments
Labels: documentation, clarification

#51 - Cash

Issue - State: closed - Opened by burdges over 4 years ago - 1 comment

#50 - Provide PDF source

Issue - State: closed - Opened by marado over 4 years ago - 1 comment
Labels: documentation

#49 - Radial antenna pattern

Issue - State: closed - Opened by rvaneijk over 4 years ago - 9 comments
Labels: bluetooth

#48 - Add recomendations about open-source or not

Issue - State: closed - Opened by gscokart over 4 years ago - 12 comments
Labels: governance, will-close-soon-without-further-input

#47 - Typos, general writing and grammar

Issue - State: closed - Opened by manulari over 4 years ago - 2 comments
Labels: documentation, clarification

#46 - Probability of success and achievability missing as key criteria for validity of proposal

Issue - State: closed - Opened by pascalwhoop over 4 years ago - 2 comments
Labels: usecases, will-close-soon-without-further-input

#45 - Circular reasoning around Breyer, both affecting trust

Issue - State: open - Opened by pdehaye over 4 years ago
Labels: legal, privacy risk

#44 - Interplay between security and data protection assessments

Issue - State: open - Opened by pdehaye over 4 years ago - 1 comment
Labels: legal, privacy risk, clarification

#43 - security and data protection-relevant actor missing: Proximity Tracking industry

Issue - State: open - Opened by pdehaye over 4 years ago - 4 comments
Labels: legal, privacy risk

#42 - Data-protection-relevant actor missing: Mobile Network Provider

Issue - State: closed - Opened by sebastianbuettrich over 4 years ago - 4 comments
Labels: legal, privacy risk, will-close-soon-without-further-input

#41 - Radio distance is not spatial distance

Issue - State: closed - Opened by sebastianbuettrich over 4 years ago - 10 comments
Labels: bluetooth, will-close-soon-without-further-input

#40 - Alerting users on contact event

Issue - State: open - Opened by maskeeter over 4 years ago
Labels: app, suggested extension, implementation

#39 - Anonymising communication metadata when communicating with the backend server.

Issue - State: closed - Opened by hiromipaw over 4 years ago - 4 comments
Labels: protocol, suggested extension, will-close-soon-without-further-input

#38 - Asymmetric signing of EphIDs to mitigate fake contacts risk

Issue - State: closed - Opened by inaitana over 4 years ago - 15 comments
Labels: protocol

#37 - Easy deanonymization of infected individuals

Issue - State: open - Opened by inaitana over 4 years ago - 9 comments
Labels: privacy risk

#36 - Use forkeable document format, not PDF

Issue - State: open - Opened by gagarine over 4 years ago - 10 comments
Labels: documentation, taken-into-account-but-not-solved-yet

#35 - Limit fake contact event attacks by using shared hashed "handshake"

Issue - State: closed - Opened by gagarine over 4 years ago - 4 comments
Labels: protocol

#34 - Why not using direct public key exchange?

Issue - State: closed - Opened by gagarine over 4 years ago - 4 comments
Labels: protocol

#33 - Why does an infected patient pick a new completely random key?

Issue - State: closed - Opened by rouvoy over 4 years ago - 3 comments
Labels: protocol

#32 - Proof of at-risk status

Issue - State: closed - Opened by bdsl over 4 years ago - 7 comments
Labels: protocol, will-close-soon-without-further-input

#31 - voluntary data release

Issue - State: closed - Opened by ekg over 4 years ago - 6 comments
Labels: protocol

#30 - aggregated mobility data

Issue - State: closed - Opened by ekg over 4 years ago - 1 comment
Labels: protocol, suggested extension

#29 - [Improvement] Getting rid of push (FCM/APN)

Issue - State: closed - Opened by laryllian over 4 years ago - 7 comments
Labels: protocol, will-close-soon-without-further-input

#28 - Clarification of the relationship between DP-3T and PEPP-PT

Issue - State: closed - Opened by pdehaye over 4 years ago - 2 comments
Labels: documentation

#27 - Infected user tracking

Issue - State: closed - Opened by muehlber over 4 years ago - 6 comments
Labels: privacy risk, will-close-soon-without-further-input

#26 - Discard GPS and use serving mobile network MCC

Issue - State: closed - Opened by ChrisDaumer over 4 years ago - 2 comments
Labels: protocol

#25 - Use of TEEs

Issue - State: closed - Opened by muehlber over 4 years ago - 2 comments
Labels: protocol

#24 - Infection reveals lots, so consider using cuckoo filters

Issue - State: closed - Opened by burdges over 4 years ago - 17 comments
Labels: protocol, privacy risk, will-close-soon-without-further-input

#23 - Is 14 days enought?

Issue - State: closed - Opened by gscokart over 4 years ago - 3 comments
Labels: usecases

#22 - user behaviour on notification of risk

Issue - State: open - Opened by pylls over 4 years ago - 4 comments
Labels: clarification, suggested extension

#21 - Misscalculation of storage and download amount?

Issue - State: closed - Opened by kreativmonkey over 4 years ago - 11 comments
Labels: protocol, will-close-soon-without-further-input

#20 - Targeted hacking can detect 2 persons met each other

Issue - State: closed - Opened by gscokart over 4 years ago - 2 comments
Labels: privacy risk

#19 - How to mitigate the risk of gamification

Issue - State: closed - Opened by gscokart over 4 years ago - 3 comments
Labels: app, usecases

#18 - Non sequential storage of ephid

Issue - State: closed - Opened by gscokart over 4 years ago - 4 comments
Labels: clarification, implementation

#17 - Some questions about the design

Issue - State: closed - Opened by ghost over 4 years ago - 10 comments
Labels: protocol, usecases, will-close-soon-without-further-input

#16 - Some thoughts on possible use cases and user groups

Issue - State: closed - Opened by ghost over 4 years ago - 6 comments
Labels: usecases

#15 - IP issue

Issue - State: closed - Opened by alexandredeleze over 4 years ago - 1 comment
Labels: protocol

#14 - Public registry of infected ids, why not the ones at risk instead?

Issue - State: closed - Opened by jasisz over 4 years ago - 2 comments
Labels: protocol

#13 - Single encounter problem

Issue - State: closed - Opened by jasisz over 4 years ago - 14 comments
Labels: protocol, privacy risk, will-close-soon-without-further-input

#12 - Other deployment scenarios and stigmatization concerns

Issue - State: closed - Opened by pdehaye over 4 years ago - 2 comments
Labels: privacy risk

#11 - Fix claims on the PEPP-PT website to match what is announced here

Issue - State: closed - Opened by pdehaye over 4 years ago - 3 comments
Labels: documentation, legal

#10 - UN Declaration of Human Rights Article 27 concerns around wording and conflation of roles

Issue - State: open - Opened by pdehaye over 4 years ago - 3 comments
Labels: documentation, legal

#9 - Data protection consequence of missing security actor

Issue - State: open - Opened by pdehaye over 4 years ago - 2 comments
Labels: documentation, legal

#8 - Involve Google -> Use existing Maps history functionality

Issue - State: closed - Opened by amalic over 4 years ago - 7 comments
Labels: protocol, legal

#7 - Bluetooth iOS implementation challenges

Issue - State: closed - Opened by gajeam over 4 years ago - 5 comments
Labels: bluetooth

#6 - Using a blockchain for backend servers

Issue - State: closed - Opened by jatorrero over 4 years ago - 4 comments
Labels: protocol

#5 - Assess existing software and systems

Issue - State: closed - Opened by nemobis over 4 years ago - 1 comment
Labels: documentation

#4 - Add a license

Issue - State: closed - Opened by nemobis over 4 years ago - 3 comments
Labels: legal

#3 - Coordinate with NOYB

Issue - State: closed - Opened by nemobis over 4 years ago - 1 comment
Labels: legal

#2 - Second visit to hospital problem

Issue - State: closed - Opened by a8x9 over 4 years ago - 2 comments
Labels: protocol

#1 - Courtesy notification

Issue - State: closed - Opened by pdehaye over 4 years ago - 3 comments
Labels: documentation

GitHub / DP-3T/documents issues and pull requests