aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2017-05-13 19:53:13 +1200
committerTom Ryder <tom@sanctum.geek.nz>2017-05-13 19:53:13 +1200
commit06b11929ea29b198a39f464c8e95f8d678f43501 (patch)
treeb0277575b4716a8585a855d8f66e3a6d769ab519
parentStrip README trailing blank line (diff)
downloadMail-Run-Crypt-06b11929ea29b198a39f464c8e95f8d678f43501.tar.gz
Mail-Run-Crypt-06b11929ea29b198a39f464c8e95f8d678f43501.zip
Remove croncryptshcroncrypt
Turned out not to be such a good idea
-rw-r--r--README.markdown15
-rwxr-xr-xbin/croncryptsh3
2 files changed, 0 insertions, 18 deletions
diff --git a/README.markdown b/README.markdown
index 4ba51ac..be1457e 100644
--- a/README.markdown
+++ b/README.markdown
@@ -16,21 +16,6 @@ The main design goal is simplicity; just whack `croncrypt` in front of all your
redirects, in which case you should consider putting it all into a script file
anyway.
-As an alternative, to apply this to all of the tasks in that `crontab(5)` file,
-you can specify `SHELL` with a fully-qualified path to the `croncryptsh`
-executable:
-
- $ crontab -l
- CRONCRYPT_KEYID=0x0A1B2C3D4E5F6G7H
- CRONCRYPT_PASSPHRASE=hibbityboo
- MAILTO=me@mynet
- SHELL=$HOME/.local/bin/croncryptsh
-
- 0 1 * * * rsync /home/tom/important-file-1 /home/backups
- 0 2 * * * rsync /home/tom/important-file-2 /home/backups
-
-This is the method the author prefers.
-
Don’t use your own GPG key for signing! I recommend you create a dedicated key
just for Croncrypt, and sign it locally with `gpg --lsign` so that your
software trusts it locally.
diff --git a/bin/croncryptsh b/bin/croncryptsh
deleted file mode 100755
index 2c25fd6..0000000
--- a/bin/croncryptsh
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/bin/sh
-exec croncrypt sh "$@"
-