Dead Man Switch

A Rust application that activates a Dead Man Switch to secure your computer in case of an emergency. The application supports multiple trigger mechanisms, including a Telegram bot, network broadcasts, and USB device detection Flic Button and more. When triggered, the Dead Man Switch dismounts VeraCrypt volumes and performs a forced hard shutdown of the system.

Features

• Trigger the Dead Man Switch using a Telegram bot, network broadcasts, USB device connection, Flic Button
• Dismount VeraCrypt volumes to secure confidential data
• Perform a forced hard shutdown of the system
• Display an emergency alert window with a countdown timer
• Customizable trigger commands and USB device detection
• Cross-platform compatibility worked on Linux Windows and macOS

Recommendations

For optimal data protection, it is highly recommended to encrypt your system partition using VeraCrypt. This ensures that all your sensitive data remains secure even if the computer is compromised or stolen. By combining the Dead Man Switch application with a VeraCrypt-encrypted system partition, you can achieve a robust security setup that safeguards your data in case of an emergency.

To encrypt your system partition with VeraCrypt, please follow the official VeraCrypt documentation and guides available on their website.

Prerequisites

• Rust programming language (1.55.0 or later)
• VeraCrypt installed on the system
• Telegram Bot API token (for the Telegram bot trigger)

Installation

1. Clone the repository:

   git clone https://github.com/BlackSnufkin/DeadManSwitch.git
   cd DeadManSwitch

2. Build the application:

   cargo build --release

Usage

Run the application with the desired trigger mode:

./target/release/DeadManSwitch --mode <mode>

Available modes:

• net: Listen for network broadcasts to trigger the Dead Man Switch
• bot: Use a Telegram bot to trigger the Dead Man Switch
• usb: Monitor USB devices and trigger the Dead Man Switch when a specific device is connected
• flic: Listen to Flic Server event trigger upon flick button click
• all: Enable all trigger modes (default)

To manually trigger the Dead Man Switch, use the --trigger flag:

./target/release/DeadManSwitch --trigger

Integration

To set up the DeadManSwitchConfig, update the configuration struct located in Lines 61-72 with your specific details.

lazy_static::lazy_static! {
    static ref CONFIG: DeadManSwitchConfig = DeadManSwitchConfig::new(
        "<TELEGRAM BOT API TOKEN>".to_string(), // Telegram bot token
        45370, // Broadcast port
        "trigger_dms".to_string(), // Broadcast message
        "execute".to_string(), // Telegram command
        0x090c, // USB vendor ID
        0x1000, // USB product ID
        "<FLIC BUTTON SERVER>".to_string(), // Flic button server IP
        5551, // Flic button server port
    );
}

Telegram Bot Command

• Create a Telegram Bot: Set up your Telegram bot using BotFather on Telegram.
• Trigger Command: Use the command /dms execute to trigger the dead man switch.

Network Broadcast Message

• Modify Broadcast Message: Update the broadcast_message field in the DeadManSwitchConfig struct with your desired message.
• Trigger Event: Send the specific broadcast message over the network to activate the dead man switch.

USB Device Detection

• Identify USB Device: Utilize the USB_mon project to find the vendor and product IDs for your USB device.
• Trigger Event: Connect the USB device to trigger the dead man switch.

Flic Button

• Set Up Flic Server: Use either the Linux Flic Server or the Windows Flic Server to pair your Flic button.
• Configure Flic Button: Update the flic_ip and flic_port fields in the DeadManSwitchConfig struct with your Flic server's IP and port.
• Trigger Event: Press and hold the Flic button to activate the dead man switch.

Disclaimer

• This application is provided "as is" without any warranty, express or implied. The authors of this project shall not be held liable for any damage, data loss, or other consequences arising from the use or misuse of this application.
• By using this application, you acknowledge that you are using it at your own risk.
• The authors of this project cannot be held responsible for any corruption of VeraCrypt containers, data loss, system instability, or any other adverse effects that may occur due to the use of this application.
• Use this application wisely and exercise caution. Always maintain backups of your important data and ensure that you have a thorough understanding of the application's functionality before using it on critical systems.