Skip to content

Issues: OpenBitcoinPrivacyProject/wallet-ratings

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

82 Open 44 Closed
82 Open 44 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

add to threat model to cover this bitcoin core rebroadcast feature
#146 opened Feb 11, 2020 by kristovatlas
Criteria: Does wallet with BIP70 support reserve a refund address? criteria questionnaire
#145 opened Mar 28, 2018 by kristovatlas 4th edition
Determine weight for temporal window for attack as a cost factor weights
#144 opened Jul 20, 2017 by kristovatlas 3rd edition
@kristovatlas
Criterion: Don't allow users to screenshot sensitive data countermeasures criteria
#143 opened Jun 1, 2017 by dcousens 4th edition
2
Network criteria: Fingerprint specific client version based on SSL cipher suites criteria
#142 opened Dec 29, 2016 by kristovatlas 4th edition
1
new criterion: wallet client uses Tor when Tor is running with default configuration criteria
#141 opened Nov 29, 2016 by kristovatlas 4th edition
Add Attacker category descriptions attackers
#140 opened Nov 14, 2016 by kristovatlas 3rd edition
@kristovatlas
10
Add Network observer attack: Identify Internet user as a Bitcoin user attacks
#139 opened Nov 14, 2016 by kristovatlas 4th edition
1
add countermeasure -- do not update blockchain data filters countermeasures criteria PR needed
#137 opened Nov 3, 2016 by kristovatlas 3rd edition
7
Countermeasure against linking IP to address based on first hop analysis: random delays attacks countermeasures criteria discussion needed
#136 opened Oct 9, 2016 by kristovatlas 4th edition
5
Determine Severity Benchmarks for 3rd edition
#135 opened Oct 5, 2016 by kristovatlas 3rd edition
18
consider rewording attacks related to change instead in terms of output ownership attacks
#134 opened Sep 25, 2016 by kristovatlas 4th edition
Alternative to creating identity containers: Just never merge heterogenous inputs countermeasures criteria
#131 opened Sep 7, 2016 by kristovatlas 4th edition
1
Re-write all criteria descriptions as questions criteria PR needed
#130 opened Sep 7, 2016 by kristovatlas 3rd edition
@kristovatlas
reword CR09 (BIP126) criteria PR needed
#129 opened Aug 31, 2016 by kristovatlas 3rd edition
@kristovatlas
RBF: changing inputs may link merged inputs not present in final version attacks countermeasures criteria
#128 opened Aug 24, 2016 by kristovatlas 4th edition
consider time of privacy breach for blockchain-based attacks attacks countermeasures criteria
#127 opened Aug 22, 2016 by kristovatlas 4th edition
4
consider detectability as a severity benchmark weights
#126 opened Aug 19, 2016 by kristovatlas 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 admin attackers attacks
#125 opened Aug 19, 2016 by kristovatlas 4th edition
consider allowing same attack to be listed under multiple attackers admin
#124 opened Aug 18, 2016 by kristovatlas 4th edition
new attack: wallet provider use order of inputs or outputs to surreptitiously leak info attacks countermeasures criteria
#123 opened Aug 18, 2016 by kristovatlas 4th edition
consider adding client fingerprinting attack to wallet provider and network observer attacks countermeasures criteria
#121 opened Aug 18, 2016 by kristovatlas 4th edition
who is the target user in the threat model? enhancement help wanted
#120 opened Aug 16, 2016 by kristovatlas
meta-attack: unfriendly contribution setting dissuades participation and thus peer inspection of source code attacks countermeasures criteria
#119 opened Aug 11, 2016 by kristovatlas 4th edition
maybe new attack -- another app on the same device captures keystrokes attacks countermeasures criteria questionnaire
#118 opened Aug 9, 2016 by kristovatlas
1
ProTip! Exclude everything labeled bug with -label:bug.