summaryrefslogtreecommitdiff
path: root/tests/static/gpg-keys
Commit message (Collapse)AuthorAge
* Remove expiration time from gpg keys in the test suiteLucas Hoffmann2019-07-21
| | | | | | | | | | | | | | | | | | | | | | | | | The keys were expired and thus the tests were failing. In order to remove the expiration time the following actions were taken: Creating a temporary directory to use as GNUPGHOME, importing all the keys: mkdir tmp export GNUPGHOME=$PWD/tmp gpg --import tests/static/gpg-keys/*sec.gpg For each of the three keys the expiration time was set to unlimited and they were reexported (the ones that were not ascii armored before were again exported without the `--armor` option): gpg --edit-key $KEY_ID gpg --export --armor $KEY_ID > $PUB_FILE gpg --export-secret-keys --armor $KEY_ID > $SEC_FILE Finally: rm -rf $GNUPGHOME unset GNUPGHOME
* tests/crypto: Add tests for the crypto moduleDylan Baker2017-07-15
This covers mosts of the functions in the crypto module, but doesn't bother with the hash_key function, which is slated for deletion in the port to python-gpg. It also doesn't cover re-raising errors.