5 ms·
Although I haven't personally set this up, my plan has been to at some point: * Put important documents and passwords in an encrypted archive or true/veracrypt
by k1t 7y ago
Although I haven't personally set this up, my plan has been to at some point:
* Put important documents and passwords in an encrypted archive or true/veracrypt container.
* Distribute the archive to relevant parties via physical media (e.g. USB stick), possibly put a public version online on somewhat reliable free hosting.
* Store the password to the archive (without any indication as to the purpose of the password) on a service such as the one in the article or an alternative, e.g. Dead Man's Switch
Because of the physical distribution of the archive, it makes it hard to change the secrets in the archive - but other than that it seems solid enough...
[1] https://www.deadmansswitch.net/ https://www.deadmansswitch.net/
- bronco21016 7y agoInteresting idea. I suppose it’s relatively low risk that the secret would be stolen and then connected with the encrypted archive. Thanks!
- deif 7y agoI created https://www.deadmantracker.com https://www.deadmantracker.com and am implementing the reverse of this but your solution is a good alternative that I might support too. The way I saw it working was: * Encrypt docs into a compressed archive * Upload encrypted docs to service * Distribute password for unencryption using something not build into the service (tell them via Signal, or Protonmail, or a piece of paper, or word of mouth) * Link for encrypted archive only becomes available once the dead mans switch is triggered In the same way a password could be uploaded and only released when the switch is triggered. A service just can't hold both parts.