PrincessPi/Encrypt-Share-Attribution
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

1779541539

Browse Source
This commit is contained in:
Princess Pi
2026-05-23 07:05:38 -06:00
parent c6394c9d45
commit 6154cebbd0
1 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+15 -2
View File
@@ -1,8 +1,15 @@
# Verifiably, Attributably Secure Archives # Verifiably, Attributably Secure Archives
For when you need to distribute information anonymously, but wish to keep it provably full and intact, but _also_ have options to prove attribution.
## Writeup ## Writeup
### Issues
- two-way deanonymization is assumed when either method to attribute is used
- when sha512 method is used, originator is assumed to be the owner of the ed25519 key and vice versa
- any reveal of either signed note or sha512 attribution passphrase, the other is assumed to belong to the same entity
- opsec failures can result in two-way deanonymization
## Usage ## Usage
### Installation
## todo ## todo
1. validate attribution thing 1. validate attribution thing
@@ -10,11 +17,17 @@
3. sanity checks 3. sanity checks
4. this README.md 4. this README.md
5. the README-instructions.txt and placedment for archive 5. the README-instructions.txt and placedment for archive
6. passphrase strength checks 6. passphrase strength/length checks
7. sha256 mode with independant passphrase 7. sha256 mode with independant passphrase(?)
8. encrypt archive option 8. encrypt archive option
1. inner 1. inner
2. outer 2. outer
9. random data optional
1. now only takes up 20Kb!
10. writeup in this README
11. usage in this README
12. specification definition
13. FileMap.md
## Changelog ## Changelog
- reduced random data to 2x 10Kb - reduced random data to 2x 10Kb