ROBERT-proximity-tracing/documents

Issues

• Why in 3.1 Server Setup is Tptsstart dynamic?

  #25 opened 5 years ago
  1

• Difference to Singapore's BlueTrace/TraceTogether

  #23 opened 5 years ago
  5

• What scenarios could be used to assess risk scores centrally, but not decentrally?

  #22 opened 5 years ago
  2

• Author names are missing

  #21 opened 5 years ago
  3

• information leaked through size/freq of client to server queries.

  #20 opened 5 years ago
  4

• Why are EPIDs only generated by server?

  #19 opened 5 years ago
  7

• Clarify 'securely erase'

  #18 opened 5 years ago
  0

• MAC verification at server end is performed last, should be first

  #17 opened 5 years ago
  2

• Deactivating 'at risk' accounts - why deactivate? what features are deactivated?

  #16 opened 5 years ago
  2

• Social/contact/proximity graph - why are they needed? Are they all same?

  #15 opened 5 years ago
  1

• Misleading: 'B and D do not get exposed' in Specification

  #14 opened 5 years ago
  0

• Clarify "Honest-but-curious" terminology

  #13 opened 5 years ago
  10

• The 'Exposure Status Request' mechanism exposes the full social graph of all users (infected or not) to the authority.

  #11 opened 5 years ago
  13

• Identification of diagnosed people by their contacts, or an active malicious agent

  #10 opened 5 years ago
  6

• TPM?

  #9 opened 5 years ago
  2

• K_S rotation?

  #8 opened 5 years ago
  4

• Inject false "at risk" status

  #7 opened 5 years ago
  19

• "authority... will need to deploy sniffing devices"

  #6 opened 5 years ago
  22

• Add a license

  #5 opened 5 years ago
  4

• Provide documents in a format that allows for feedback and discussion

  #4 opened 5 years ago
  5

• Do not use 3DES as a potential block-cipher

  #3 opened 5 years ago
  4

• Pseudonyms Generated and Managed by Authority, Communicated to Users

  #2 opened 5 years ago
  7

• Is this part of PEPP-PT?

  #1 opened 5 years ago
  5