1
1
=== SUMMARY ===
2
2
3
+ version: 1.0.5
4
+
3
5
You deleted your only copy of an OpenPGP private key file. You wonder if the key
4
6
material can be recovered via forensic techniques such as file carving.
5
7
( https://en.wikipedia.org/wiki/File_carving ) Happily you're in luck! Dodge
6
8
(named after the key obsessed demon in Locke & Key show) may be able to help!
7
9
8
- === VERSION ===
9
-
10
- 1.0.4
11
-
12
10
=== USAGE ===
13
11
14
12
Basic usage:
@@ -60,10 +58,11 @@ just for well off people with reliable Internet access. Learn more at:
60
58
https://makesourcenotcode.github.io/freedom_respecting_technology.html
61
59
62
60
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 )
67
66
68
67
=== MOTIVATION AND DEVELOPMENT NOTES ===
69
68
@@ -81,6 +80,8 @@ That story is Thoroughly Entertaining. But for those short on time pages 67-75
81
80
contain the critical details you need to try that approach as well. Page 80 of
82
81
the slides is the approach I believe in retrospect would have been best.
83
82
83
+ The corresponding video may also prove amusing: https://vimeo.com/341007205
84
+
84
85
Namely find all offsets for the '-----BEGIN PGP PRIVATE KEY BLOCK-----' bytes in
85
86
the image, read some chunk of data from each such offset storing it in a
86
87
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.
165
166
166
167
=== CHANGELOG ===
167
168
169
+ v1.0.5: improved documentation
168
170
v1.0.4: leverage grep more idiomatically
169
171
v1.0.3: fix documentation bugs
170
172
v1.0.2: fix documentation bugs
0 commit comments