After reading about the “suicide” of yet another whistleblower, it got me thinking.

When working at large enough company, it’s entirely possible that at some point you will get across some information the company does not want to be made public, but your ethics mandate you blow the whistle. So, I was wondering if I were in that position how I would approach creating a dead man’s switch in order to protect myself.

From wikipedia:

A dead man’s switch is a switch that is designed to be activated or deactivated if the human operator becomes incapacitated, such as through death, loss of consciousness, or being bodily removed from control. Originally applied to switches on a vehicle or machine, it has since come to be used to describe other intangible uses, as in computer software.

In this context, a dead man’s switch would trigger the release of information. Some additional requirements could include:

  1. No single point of failure. (aka a usb can be stolen, your family can be killed, etc)
  2. Make the existence of the switch public. (aka make sure people know of your mutually assured destruction)
  3. Secrets should be safe until you die, disappear, or otherwise choose to make them public.

Anyway, how would you go about it?

  • preludeofme@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    6 hours ago

    I used to build automation tools (shudderVBAshudder) that the “proper” technology wouldn’t be bothered to make. Over 15 years I had over 200 tools built out. I had tied all my code to a single file that I would use to keep everything updated. I had imagined in so many ways of setting up a dead man’s switch to start slowly corrupting and degrading everything or to just implode everything… Would have worked except our company got bought out and everything became useless and I got laid off lol. Got a nice pay check out of it