Issues

• add to threat model to cover this bitcoin core rebroadcast feature

  OpenBitcoinPrivacyProject/wallet-ratings#146 · Filter by author kristovatlas opened on Feb 11, 2020

• Criteria: Does wallet with BIP70 support reserve a refund address?

  criteriaquestionnaire
  OpenBitcoinPrivacyProject/wallet-ratings#145 · Filter by author kristovatlas opened on Mar 28, 2018 · 4th edition

• Determine weight for temporal window for attack as a cost factor

  weights
  OpenBitcoinPrivacyProject/wallet-ratings#144 · Filter by author kristovatlas opened on Jul 20, 2017 · 3rd edition
  

• Criterion: Don't allow users to screenshot sensitive data

  countermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#143 · Filter by author dcousens opened on Jun 1, 2017 · 4th edition
  2

• Network criteria: Fingerprint specific client version based on SSL cipher suites

  criteria
  OpenBitcoinPrivacyProject/wallet-ratings#142 · Filter by author kristovatlas opened on Dec 29, 2016 · 4th edition
  1

• new criterion: wallet client uses Tor when Tor is running with default configuration

  criteria
  OpenBitcoinPrivacyProject/wallet-ratings#141 · Filter by author kristovatlas opened on Nov 29, 2016 · 4th edition

• Add Attacker category descriptions

  attackers
  OpenBitcoinPrivacyProject/wallet-ratings#140 · Filter by author kristovatlas opened on Nov 14, 2016 · 3rd edition
  10

  

• Add Network observer attack: Identify Internet user as a Bitcoin user

  attacks
  OpenBitcoinPrivacyProject/wallet-ratings#139 · Filter by author kristovatlas opened on Nov 14, 2016 · 4th edition
  1

• add countermeasure -- do not update blockchain data filters

  countermeasurescriteriaPR needed
  OpenBitcoinPrivacyProject/wallet-ratings#137 · Filter by author kristovatlas opened on Nov 3, 2016 · 3rd edition
  7

• Countermeasure against linking IP to address based on first hop analysis: random delays

  attackscountermeasurescriteriadiscussion needed
  OpenBitcoinPrivacyProject/wallet-ratings#136 · Filter by author kristovatlas opened on Oct 9, 2016 · 4th edition
  5

• Determine Severity Benchmarks for 3rd edition

  OpenBitcoinPrivacyProject/wallet-ratings#135 · Filter by author kristovatlas opened on Oct 5, 2016 · 3rd edition
  18

• consider rewording attacks related to change instead in terms of output ownership

  attacks
  OpenBitcoinPrivacyProject/wallet-ratings#134 · Filter by author kristovatlas opened on Sep 25, 2016 · 4th edition

• Alternative to creating identity containers: Just never merge heterogenous inputs

  countermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#131 · Filter by author kristovatlas opened on Sep 7, 2016 · 4th edition
  1

• Re-write all criteria descriptions as questions

  criteriaPR needed
  OpenBitcoinPrivacyProject/wallet-ratings#130 · Filter by author kristovatlas opened on Sep 7, 2016 · 3rd edition
  

• reword CR09 (BIP126)

  criteriaPR needed
  OpenBitcoinPrivacyProject/wallet-ratings#129 · Filter by author kristovatlas opened on Aug 31, 2016 · 3rd edition
  

• RBF: changing inputs may link merged inputs not present in final version

  attackscountermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#128 · Filter by author kristovatlas opened on Aug 24, 2016 · 4th edition

• consider time of privacy breach for blockchain-based attacks

  attackscountermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#127 · Filter by author kristovatlas opened on Aug 22, 2016 · 4th edition
  4

• consider detectability as a severity benchmark

  weights
  OpenBitcoinPrivacyProject/wallet-ratings#126 · Filter by author kristovatlas opened on Aug 19, 2016 · 3rd edition

• review the network observer, transaction participant, and wallet provider attacks to look for attacks that should be listed commonly but are not yet

  adminattackersattacks
  OpenBitcoinPrivacyProject/wallet-ratings#125 · Filter by author kristovatlas opened on Aug 19, 2016 · 4th edition

• consider allowing same attack to be listed under multiple attackers

  admin
  OpenBitcoinPrivacyProject/wallet-ratings#124 · Filter by author kristovatlas opened on Aug 18, 2016 · 4th edition

• new attack: wallet provider use order of inputs or outputs to surreptitiously leak info

  attackscountermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#123 · Filter by author kristovatlas opened on Aug 18, 2016 · 4th edition

• consider adding client fingerprinting attack to wallet provider and network observer

  attackscountermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#121 · Filter by author kristovatlas opened on Aug 18, 2016 · 4th edition

• who is the target user in the threat model?

  enhancementhelp wanted
  OpenBitcoinPrivacyProject/wallet-ratings#120 · Filter by author kristovatlas opened on Aug 16, 2016

• meta-attack: unfriendly contribution setting dissuades participation and thus peer inspection of source code

  attackscountermeasurescriteria
  OpenBitcoinPrivacyProject/wallet-ratings#119 · Filter by author kristovatlas opened on Aug 11, 2016 · 4th edition

• maybe new attack -- another app on the same device captures keystrokes

  attackscountermeasurescriteriaquestionnaire
  OpenBitcoinPrivacyProject/wallet-ratings#118 · Filter by author kristovatlas opened on Aug 9, 2016
  1