aboutsummaryrefslogtreecommitdiff
path: root/lib/keyringer/actions/canary
blob: aa669265d4f73f56fcf3af74b074512e0d1a5e6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
#!/bin/bash
#
# Keyringer's canary warrant implementation.
#
# Inspired by:
#
#   https://en.wikipedia.org/wiki/Warrant_canary
#   http://www.rsync.net/resources/notices/canary.txt
#
# A canary is:
#
#   - Generated using any combination of public available RSS
#     feeds configured by user preferences.
#
#   - Configured to generate new information once a day.
#     If you run it more than once in this time span, no canary
#     will be updated.
#
# A canary is stored:
#
#   - In a folder called "canaries" followed by the user ID.
#
#   - With an addiditonal timestamp stored plain+signed so it
#     can be easily checked.
#
#   - Can optionally be uploaded (encrypted or plain+signed) to a
#     remote url via scp.
#
#   - Can optionally be included in another git repository
#     (encrypted or plain+signed), commited and pushed
#     to a remote repository (ikiwiki instance, etc).
#
# How to run:
#
#  - First, "keyringer <keyring> preferences edit # basic canary preferences".
#
#  - Then, add the following to your ~/.profile or wherever you want your canary
#    be called from: "keyringer <keyring> canary".

# Load functions
LIB="`dirname $0`/../functions"
source "$LIB" || exit 1

# TODO: code!
echo "Not implemented :("
exit 1