aespipe-wrapper-0.49 README
Description
===========
This is simply a thin convenience wrapper around aespipe*. The aespipe
utility acts as a filter (reading from STDIN, writing to STDOUT), but it
also reads a set of keys on a separate file descriptor. There are two
sets of keys involved in the operation of this script.
aespipe uses a set of AES keys for encrypting your stream of data
GPG encrypts the AES keys, so they aren't stored unsafely on disk
NOTE: During encryption, aespipe null-pads the end of the file to reach
a block boundary. During decryption, aespipe does not remove
these nulls, so the checksum of the initial file and the
decrypted will differ. Compression utilities are comfortable
stripping the nulls, so consider using bzip2/gzip before
passing the data to aespipe.
Modes
=====
Encryption (--encrypt): To accommodate automated encryption, aespipe-wrapper
does the following:
1. it does not ask for passwords or passphrases from the terminal in
encryption mode (suitable for fully automated use)
2. it generates a keyset suitable for aespipe encryption
3. it stores the keyset in the specified keyfile, encrypted using GPG
public key cryptography to an arbitrary set of recipients
4. finally, it calls aespipe, feeding STDIN, STDOUT and keys
Decryption (--decrypt): Decryption is simpler. The wrapper simply
calls aespipe with the provided keyfile and the input and output
redirections in place.
Creation (--create): Key creation is a simple way to test that everything is working, and is
only supplied as a convenience.
The user must always:
- specify a keyfile with the -k (--keyfile) option
- specify an action (--decrypt, --encrypt or --create)
If you have a need to pass options through to aespipe itself, simply place
them after \"--\", and they will be passed through directly to aespipe.
See the example section below.
Options
=======
aespipe-wrapper operates on STDIN and STDOUT, as any good filter. It provides
the compatibility options --input (-i) and --output (-o) for convenience.
Usually, data collected by the pseudo-random device (/dev/urandom) is
suitably random to use in cryptography, although many people prefer to
use a real random source (e.g., /dev/random). Because of the possibility
for program delay awaiting random data, the default option is the
pseudo-random device.
If no GPG recipient