Skip to content

Commit bf38fa9

Browse files
improved documentation
1 parent bb1b0c1 commit bf38fa9

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

README.txt renamed to README.dodge_help_information

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,12 @@
11
=== SUMMARY ===
22

3+
version: 1.0.5
4+
35
You deleted your only copy of an OpenPGP private key file. You wonder if the key
46
material can be recovered via forensic techniques such as file carving.
57
( https://en.wikipedia.org/wiki/File_carving ) Happily you're in luck! Dodge
68
(named after the key obsessed demon in Locke & Key show) may be able to help!
79

8-
=== VERSION ===
9-
10-
1.0.4
11-
1210
=== USAGE ===
1311

1412
Basic usage:
@@ -60,10 +58,11 @@ just for well off people with reliable Internet access. Learn more at:
6058
https://makesourcenotcode.github.io/freedom_respecting_technology.html
6159

6260
It's (admittedly small) Open Knowledge Set consists of:
63-
* the main program source/executable file dodge
64-
licensed under GNU GPL v3 ( https://www.gnu.org/licenses/gpl-3.0.txt )
65-
* the documentation / Help Information Set consisting of this file
66-
licensed under GNU FDL v1.3 ( https://www.gnu.org/licenses/fdl-1.3.txt )
61+
* the main program source file / executable file dodge licensed under
62+
GNU GPL v3 ( https://www.gnu.org/licenses/gpl-3.0.txt )
63+
* the source / built form of the documentation / Help Information Set consisting
64+
of this file licensed under
65+
GNU FDL v1.3 ( https://www.gnu.org/licenses/fdl-1.3.txt )
6766

6867
=== MOTIVATION AND DEVELOPMENT NOTES ===
6968

@@ -81,6 +80,8 @@ That story is Thoroughly Entertaining. But for those short on time pages 67-75
8180
contain the critical details you need to try that approach as well. Page 80 of
8281
the slides is the approach I believe in retrospect would have been best.
8382

83+
The corresponding video may also prove amusing: https://vimeo.com/341007205
84+
8485
Namely find all offsets for the '-----BEGIN PGP PRIVATE KEY BLOCK-----' bytes in
8586
the image, read some chunk of data from each such offset storing it in a
8687
temporary file, try importing that temporary file with GnuPG which shouldn't be
@@ -165,6 +166,7 @@ single time I tried using it. Your luck may be better.
165166

166167
=== CHANGELOG ===
167168

169+
v1.0.5: improved documentation
168170
v1.0.4: leverage grep more idiomatically
169171
v1.0.3: fix documentation bugs
170172
v1.0.2: fix documentation bugs

0 commit comments

Comments
 (0)