re-share.encryption — re-share 0.17.0

pgp secret encryption support, in order to test we can generate a testing keyring:

gpg --no-default-keyring --keyring trustedkeys.gpg --fingerprint

gpg --no-default-keyring --keyring trustedkeys.gpg --gen-key

A public and private keyrings should be exported (for bountycastle support):

gpg --no-default-keyring --keyring trustedkeys.gpg --export >> test/resources/public.gpg

gpg --no-default-keyring --keyring trustedkeys.gpg --export-secret-keys >> test/resources/secret.gpg

alpha-numeric clj

decode clj

(decode s)

decrypt clj

(decrypt encrypted secret-key pass)

Unlock secret and decrypt encrypted string (key isn't cached)

encode clj

(encode bs)

encrypt clj

(encrypt input public-key)

Load public key and encrypt input

list-private clj

(list-private k)

list-public clj

(list-public k)

load-private clj

(load-private path)

load-public clj

(load-public path)

random-str clj

(random-str l)

read-pass clj

(read-pass)

Under both lein run and lein repl (System/console) is nil, we use following workaround (works only under tmux):

1. Create a tmux window and use read -s to write the password into a file.
2. Read the file and delete it. Note:
3. This isn't as secure as System/console readPassword but still better than reading the password in the clear.
4. We assume that we run under tmux (no check is made)