| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
that tests if a message with unknown content-transfer-encoding header,
but otherwise correct ascii encoded payload, is warned about.
|
| |
|
|
|
|
| |
This adds a test for detecting a malformed content-transfer-encoding
(trailing semi-colon).
It also changes the raised exception to the more appropriate ValueError.
|
| |
|
|
|
| |
The test corpus holds mails that are used to test different problems
with parsing or displaying mail.
|
| |
|
|
|
|
| |
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.
|
|
|
This adds a couple of basic tests for the signing and verification of
signatures code in the crypto module. This relies on the utilities
module introduced in the last patch.
One of the tests in here is expected to fail
|
