this post was submitted on 11 Jan 2025
182 points (97.9% liked)

Asklemmy

44331 readers
1032 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy πŸ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
 

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?

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 167 points 4 days ago* (last edited 4 days ago) (8 children)

The most non-intrusive foolproof method I can think of is spite-induced action:

  1. Get a pacemaker with Zigbee mesh network connectivity
  2. Implant a small device into your wrist that vibrates if your pacemaker is ever disconnected from the network (in which case, run NOW to your nearest safehouse)
  3. Should the vibration continue for longer than 5 minutes, a vial of cyanide from a hollow tooth explodes into your mouth allowing you to spit it at your nearest enemy (should one be around)
  4. The bursting of the hollow tooth sends a signal to a remote server, which triggers the eject command on a server, causing the CD tray to come out.
  5. A confused sysadmin will bitterly get off his chair, and go inspect the server, whereupon he will see the paper instructions embedded in the CD tray, and read them.
  6. Assuming his latvian is good, and that he's familiar with caesar cyphers, he will decode the message that will lead him to a youtube URL where he will post the following comment "Jose I slept with your mother."
  7. One of the subscribers to the youtube channel is your friend Jose, who will read the comment, spit out his coffee, and then immediately call you.
  8. After about a week of no response, he uploads the contents of that USB stick you gave him with the instructions to "never upload this ever under any circumstance" out of sheer spite.

Edit: Here, I made a diagram of the whole thing

State Diagram

spoiler (with mermaid source)

stateDiagram-v2
    direction TB
    
    state Internet {
        state "Wider Zigbee Network" as WiderZigbeeNetwork
        --
        state "Youtube" as youtube{
            state "MuckBang
            <small>Wasabi Challenge</small>" as video1
            state "A Cat's Guide to Vomit
            <small>By Remington Steel</small>" as video2
        }        
        state "Remote Server" as server {
            state "Server
            <small>CD-Tray</small>" as cdtray
            state "SysAdmin
            <small>Some Latvian Dude</small>" as terry
        }
        --
        state "brazzers.org" as brazzers
    }

    state People {
        state "Jose" as jose {
           state "Youtube Subscriptions" as subs
            state "Phone" as josephone
            state "Coffee" as cuppajoe
            state "USB Stick" as usb2
        }
        state "You" as you {
            state "Pacemaker" as pmaker
            state "Wrist Implant" as wrimplant
            state "Hollow Tooth" as htooth
            state "USB Stick" as usb1
            state "Phone" as youphone
        }
        state "Enemy" as enemy {
            state "Random Person" as rando
        }
    }

    [*] --> pmaker : Insert next to heart
    pmaker --> WiderZigbeeNetwork : Maintain connection
    WiderZigbeeNetwork --> wrimplant : Vibrate for 5 mins if connection lost
    wrimplant --> htooth: Explode after 5 mins vibrating

    htooth --> cdtray: Send "eject"
    htooth --> enemy: Spit cyanide
    cdtray --> terry : Decode the paper in the CD tray
    terry --> video1 : Comment about Jose's mother

    video1 --> subs : subscribed to
    video2 --> subs : subscribed to

    subs --> cuppajoe : Spit out when reading insulting comment
    cuppajoe --> usb2
    cuppajoe --> josephone

    usb1 --> usb2 : Years ago - Give USB stick with instructions to never upload
    josephone --> youphone : Call to complain but get no response
    usb2 --> brazzers : Upload USB contents out of spite

:::

[–] [email protected] 47 points 4 days ago (1 children)

This reads like a modern day SysAdmin Rube Goldberg machine; I love it

[–] [email protected] 1 points 2 days ago

Worthy of being submitted to The Register as a sysadmin story

[–] [email protected] 18 points 4 days ago (1 children)
[–] [email protected] 10 points 4 days ago

Woa, I was reading this as the Edit federated in and it refreshed. Trippy.

[–] [email protected] 9 points 4 days ago
load more comments (4 replies)
[–] [email protected] 104 points 4 days ago (4 children)

The real answer: hire a law firm, entrust them with your documents, write into your will what you want to happen with them, and then go on about your business.

[–] [email protected] 26 points 4 days ago

Maybe, add a clause what should happen if you disappear for more than x days. For most jurisdictions you are considered dead if you disappear for a few years.

[–] [email protected] 16 points 4 days ago (1 children)

The question assumes that you family could be killed. Why the law firm is protected against such violence in that case?

[–] [email protected] 15 points 4 days ago* (last edited 4 days ago)

A dead man's switch doesn't quite protect you from garden hose cryptanalysis though. Nothing stops them from asking you to tell them if he got a dead man's switch.

[–] [email protected] 6 points 3 days ago

This is only partially true in the situation the poster named. What if your secrets are from the government or governmental organization? What if you live under a repressive regime where the law firms are either corrupt or that the law is not in your favor?

That being said, I have a will and a bank safe deposit box. It is filed with the state that I have a will and the will is (also) in the safe deposit box along with stuff that I'd prefer not be released until my death. There's also a clause in the will that says something to the effect that if somebody sues to invalidate the will, they are automatically excluded from any benefit (or responsibilities). Also, if an individual is found to be somehow responsible or had an intentional involvement in my death, then they are also excluded.

It's not air tight, but works for my needs. By the way, I don't have any company or government secrets, it's just normal family drama, so please don't kill me.

load more comments (1 replies)
[–] [email protected] 6 points 2 days ago (1 children)

Set up several solar powered raspberry pies with cheap iot SIM cards, each will check a vm in the cloud or at home for a key. If the key isn’t present or can’t be reached they release the info. Could have several servers to store keys to check. Everyday you enter a code to prevent the key from being removed.

[–] [email protected] 9 points 2 days ago

You would need to account for temporary connection issues to make sure it doesn't send it after a network outage or something.

[–] [email protected] 68 points 4 days ago (8 children)

Encrypt secret. Post it publicly. Configure a web server to email the private key to any number of addresses if you don’t log in every week.

[–] [email protected] 42 points 4 days ago (1 children)

going to have to be careful with the timing, though. A week can easily be reached if you are ever in an (actual) accident.

Also, note that having a publicly known dead mans switch can be exploited and cause the opposite of what you want: Imagine a competitor (be it idustrial or nation state) wants the secret to leak. Why not speed it up?

[–] [email protected] 11 points 4 days ago

The thought of e.g. some foreign adversary having you KILLED just so your secret leaks… that’s wild.

load more comments (7 replies)
[–] [email protected] 9 points 3 days ago (1 children)

It doesn't make any sense. If you are a whistleblower is because you already published the information. They are not killing you so the information does not get revealed. They are killing because you already did.

load more comments (1 replies)
[–] [email protected] 13 points 3 days ago (2 children)

Making the existence of the switch public is often something you don't want. It allows others to do troubleshooting in advance. It also destroys your reputation with many people who might otherwise work with you.

If you are content to keep things secret, share the documents with several different friends or law firms in several different countries along with conditions for release. Don't tell them or everyone who all has the documents. That sounds relatively simple.

[–] [email protected] 3 points 3 days ago

Making the existence of something public means you'd need to give away at least some details of who or what it concerned, at which point you're in the situation of either being a target or a blackmailer.

load more comments (1 replies)
[–] [email protected] 40 points 4 days ago* (last edited 4 days ago) (1 children)

There are very few situations where a dead man's switch would have helped these whistleblowers.

Once they have gone public and are at risk of being "suicided" they should have already released everything they knew. Sitting on it after already going public in any way only helps if the goal is to blackmail or extort the company, rather than to expose the company or protect others.

A lot of people have latched onto the idea of a dead man's switch (and I get it, technical solutions are fun to create), but the only part of the scenario it would help is before the whistleblower goes public, while they are still gathering information and haven't yet been discovered by the company. Even then, it wouldn't protect them from being killed, it would only ensure that the partial work is released in case they were discovered and prevented from finishing it.

[–] [email protected] 25 points 4 days ago (3 children)

A "live-man's switch" might be a better idea. If you're in such a high profile situation and you're scared enough that you think you need a dead man's switch, make frequent unprompted public declarations that you're healthy and not suicidal, and that should anything happen to you, you blame the company.

[–] [email protected] 11 points 3 days ago

Btw, that sounds a lot like warrant canaries, where you say that no subpoena orders were recieved as of the date xxxx and if it doesn't get updated it means that a subpoena was recieved.

Wikipedia article: https://en.m.wikipedia.org/wiki/Warrant_canary

An example of a canary from the web mail service cock.li: https://cock.li/canary.asc.txt

[–] [email protected] 10 points 4 days ago

Interesting!

make frequent unprompted public declarations that you're healthy and not suicidal

I’ve worried that this could be abused

load more comments (1 replies)
[–] [email protected] 26 points 4 days ago (3 children)

Just a scheduled email that you need to cancel every 24 hours.

load more comments (3 replies)
[–] [email protected] 29 points 4 days ago (2 children)

If you really have secrets, you shouldn't have a dead man's switch.

You should have released it all on day one.

"What makes them keep you alive then?"

It's not like corporations are going to get punished for killing you regardless.

[–] [email protected] 29 points 4 days ago

The problem with releasing them on day one is that you then can't gather more. If you've only just exposed the edges of the malfeasance you need time to get the rest before exposing it. Go too early and the rest of the evidence can be destroyed, covered up or those holding it coearsed into silence.

Having a dead man's switch is a way to ensure whatever you've gathered gets released if you're no longer in a position to gather more. As such I disagree with the poster about making it public knowledge before release. Keep it secret until you have everything, then release it.

[–] [email protected] 16 points 4 days ago (1 children)

Another thing to consider is that you won't know immediately that the information you stumbles upon is incriminating. Sometimes it may take years until you have all the pieces of the puzzle.

load more comments (1 replies)
[–] [email protected] 13 points 3 days ago

4, 8, 15, 16, 23, 42

[–] [email protected] 13 points 3 days ago (4 children)

This one works if you are an inbox-zero sort of person. Write a script to send yourself an email daily. Have another utility look for your reply. If you go too long without replying, have it trigger whatever other emails/actions you would like to happen.

load more comments (4 replies)
[–] [email protected] 9 points 3 days ago (1 children)

The whole point in being a whistleblower is to release the documents. Why would you tell everyone what's happening and not provide the evidence? After you release it, there's less chance of being harmed, and your job is done besides showing up to court.

load more comments (1 replies)
[–] [email protected] 7 points 3 days ago (7 children)

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

load more comments (7 replies)
[–] [email protected] 9 points 3 days ago (1 children)

Pretty easy if you don’t work for google.

  1. Upload everything to a google drive.
  2. setup inactive account manager
  3. add all the news agencies you can get a hold of, government offices, police etc.
  4. make sure it’s read only access.

If they want to silence you they have to 1. Know about your account. 2. Keep it active.

[–] [email protected] 10 points 3 days ago* (last edited 3 days ago) (1 children)

It relies on the news agencies and such actually caring.

As someone who's been fighting a huge fight against a casino threatening my performance home, lemme tell you that most don't give a single shit

load more comments (1 replies)
[–] [email protected] 17 points 4 days ago (2 children)

The fuck kind of information you sitting on there!?

[–] [email protected] 15 points 4 days ago (1 children)

He knows the real identity of the Hamburgler

load more comments (1 replies)
load more comments (1 replies)
[–] [email protected] 9 points 3 days ago* (last edited 3 days ago) (1 children)

Depends on your background and industry.

If you work in IT, and are technically adept, you can...

  1. Store said files on a proton drive or mega.nz drive set to be only accessible to read by those who have the unique URL.
  2. Create a small server with a cron job that every 24 hours sends you a text message to a Google Voice number accessible anywhere with internet connectivity and you have 60 seconds to reply otherwise the cron job will craft a premade email to all international news agencies as well as government agencies responsible for the control of this issue, along with links to download the information.
[–] [email protected] 17 points 3 days ago* (last edited 3 days ago) (1 children)

60 seconds in 24 hours seems too prone to the possibility of a false positive. What if you forget and take a nap? What if there's a power outage? What if your phone breaks unexpectedly?

[–] [email protected] 6 points 3 days ago (1 children)

All good points, however the purpose of a deadman's switch is that you fear for your life, taking a nap might not be as easy under those circumstances. Also, if you know at what time the SMS is set to arrive you can plan ahead to make sure you have Internet in order to respond, but OK maybe 60 seconds is too short of a time so let's make it 5 minutes. Being that this is using Google Voice, you can receive the SMS over a tablet or laptop so a backup would be a must have.

[–] [email protected] 5 points 3 days ago (2 children)

Even 5 minutes seems short. You're already dead, what's the rush?

load more comments (2 replies)
[–] [email protected] 5 points 3 days ago (4 children)

A whistleblower doesn't need a dead man's switch as they'd just release the document.

A muckracker does.

load more comments (4 replies)
[–] [email protected] 10 points 4 days ago

Nice try Boeing.

My lips are sealed

[–] [email protected] 10 points 4 days ago (1 children)

Give the encrypted file to one person, the key to another and do not keep either yourself. They exchange them if you die.

[–] [email protected] 12 points 4 days ago (1 children)

Why not keep a copy?

Also, both people are single point of failures. Maybe, 5-6 people where each has an encrypted payload and the keys to decrypt everyone else's payload.

load more comments (1 replies)
load more comments
view more: next β€Ί