Define an empty "encrypt" command
Fix the keyring that we use for testing

The original keyring that we generated was not created properly -- it
had trust issues (ha) and did not have a proper copy of its own private
key.

This keyring was generated via the command-line gpg tools, which do a
much more thorough job. The only downside is that they only seem to work
on the .gnupg directory that's in your home directory. So you need to
move your own keyring aside to properly create a new keyring like this
one.
Encrypt a given file for a single hard-coded recipient

There is not much robustness here, but we're encrypting and decrypting a
file, which is a good start.
Create "bob" and "alice" keyrings

We'll need two separate keyrings like this for verifying who can read
what.
Ensure that bob can't read a file that's destined for alice
Move common repository operations to module
Add helpers to swap gpg identities
Set up bob's and alice's keyrings fresh each time
Simplify import spec

Take advantage of helper methods and better built in matchers.
Consolidate definition of fixtures_path
Simplify encrypt spec
Merge pull request #4 from psu-stewardship/encrypt

Encrypt base functionality is setup