From: Silvio Rhatto Date: Tue, 25 Feb 2014 18:56:54 +0000 (-0300) Subject: Canary will be coded in a separate branch X-Git-Tag: 0.3.1~15 X-Git-Url: https://gitweb.fluxo.info/?a=commitdiff_plain;h=e33b8aa1d3a8377abccb738b6af163b1881bb708;p=keyringer.git Canary will be coded in a separate branch --- diff --git a/ChangeLog b/ChangeLog index 615902d..dd2dc8d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,6 @@ -2014-02-24 - Silvio Rhatto +2014-02-25 - Silvio Rhatto - Starting to code new actions: check (#39) and canary (#40) + New action: check (#39) Enhanced secret finder at keyringer_get_file and on find action diff --git a/lib/keyringer/actions/canary b/lib/keyringer/actions/canary deleted file mode 100755 index b00926d..0000000 --- a/lib/keyringer/actions/canary +++ /dev/null @@ -1,46 +0,0 @@ -#!/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 that interval, 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 optinally 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 preferences edit # basic canary preferences". -# -# - Then, add the following at your ~/.profile or wherever you want your canary -# be called from: "keyringer canary". - -# Load functions -LIB="`dirname $0`/../functions" -source "$LIB" || exit 1 - -# TODO: code! -echo "Not implemented :(" -exit 1