DMH will execute action when you will not be able to. Dead-man-switch software with privacy in mind.
DMH will execute action when you will not be able to. Dead-man-switch software with privacy in mind.
Dead-Man-Hand will execute pre-added actions when you will no longer be "available".
All actions are encrypted and when properly configured nobody will be able to get action details until you are dead.
Main goal of DMH is to ensure that actions can be executed only when you are dead. And before that time, every action should be confidential - even for people who have access to DMH.
DMH you will not be able to see action details.json_post, bulksms, mail, exec)release encryption private key when user will be considered dead)min_interval: 0).To decrypt action, access to DMH and Vault is required - DMH stores encrypted data and Vault stores encryption key.
To provide best possible privacy/security, its required to run DMH and Vault on different systems/servers/locations.
docker run --name dead-man-hand -e DMH_CONFIG_FILE=/data/config.yaml -v /srv/dead-man-hand/data:/data -p 8080:8080 ghcr.io/bkupidura/dead-man-hand:latestThe image runs as a non-root user (uid:gid 1000:1000). /srv/dead-man-hand/data must be writable by dmh user (chown -R 1000:1000 /srv/dead-man-hand/data)
golanggit clone https://github.com/bkupidura/dead-man-hand.gitcd dead-man-hand && make buildDMH_CONFIG_FILE=config.yaml ./dmhDMH is easily extensible and support below plugins:
dummy - log action messagejson_post - send HTTP POST requestmail - send mail over SMTPbulksms - send SMS with bulksms.comexec - run a local binary/scriptDocumentation is available in wiki
No open issues yet, or sync has not completed.