M.A.I.D.: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
JeffreyATW (talk | contribs) m (Reverted edits by Rubin109 (talk) to last revision by JeffreyATW) |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
MAID is (Mutually) Assured Information Destruction: ''"Maid cleans up after you're no longer around."'' | MAID is (Mutually) Assured Information Destruction: ''"Maid cleans up after you're no longer around."'' | ||
== General overview == | |||
M.A.I.D. is a framework that provides time sensitive remote key escrow and provable authentication with optional distress coding. It automatically destroys cryptographic keys after a given user configurable time threshold is crossed. | M.A.I.D. is a framework that provides time sensitive remote key escrow and provable authentication with optional distress coding. It automatically destroys cryptographic keys after a given user configurable time threshold is crossed. | ||
== Features == | == Features == | ||
| Line 36: | Line 27: | ||
== History == | == History == | ||
M.A.I.D was [ | M.A.I.D was [https://events.ccc.de/congress/2005/fahrplan/events/1112.en.html initially discussed] by it's creator [[User:Ioerror|Jacob Appelbaum]] at the Chaos Computer Club's 22nd Communications Congress in the winter of 2005. | ||
Latest revision as of 09:28, 5 October 2017
MAID is (Mutually) Assured Information Destruction: "Maid cleans up after you're no longer around."
General overview[edit | edit source]
M.A.I.D. is a framework that provides time sensitive remote key escrow and provable authentication with optional distress coding. It automatically destroys cryptographic keys after a given user configurable time threshold is crossed.
Features[edit | edit source]
- Provable authentication (with either local or remote attestation)
- Cryptographic key storage on remote systems
- Optional distress coding during authentication
- Time sensitive user configurable key destruction
- Strong multi-party anonymity is a requirement for participation.
Threat model[edit | edit source]
Example use case[edit | edit source]
Software specification[edit | edit source]
Client specification[edit | edit source]
Server specification[edit | edit source]
Legal information[edit | edit source]
We believe this system will possibly work exactly one time for a single person. Consult with a qualified lawyer or solicitor in your legal jurisdiction. You may be that single lucky person.
History[edit | edit source]
M.A.I.D was initially discussed by it's creator Jacob Appelbaum at the Chaos Computer Club's 22nd Communications Congress in the winter of 2005.