summaryrefslogtreecommitdiff
path: root/alot/db/utils.py
diff options
context:
space:
mode:
authorDylan Baker <dylan@pnwbakers.com>2017-07-26 19:49:08 -0700
committerDylan Baker <dylan@pnwbakers.com>2017-08-17 10:59:49 -0700
commit72f38d180ebba19b5479ded08f6df0acd7acd7d2 (patch)
treefd68aab893b62031972e3c096a1d90fd7cef855e /alot/db/utils.py
parentcff9f149458c2e8742c7aa344984c3bf1d741747 (diff)
db/utils: Don't attach invalid signature to unsigned but encrypted messages
The logic in the comment is faulty. There are perfectly legitimate reasons to encrypt but not sign a message, some of them are fleshed out in the previous commit.
Diffstat (limited to 'alot/db/utils.py')
-rw-r--r--alot/db/utils.py5
1 files changed, 0 insertions, 5 deletions
diff --git a/alot/db/utils.py b/alot/db/utils.py
index 994e85b2..8f71f20a 100644
--- a/alot/db/utils.py
+++ b/alot/db/utils.py
@@ -203,11 +203,6 @@ def message_from_file(handle):
for k in (X_SIGNATURE_VALID_HEADER,
X_SIGNATURE_MESSAGE_HEADER):
m[k] = n[k]
- else:
- # an encrypted message without signatures
- # should arouse some suspicion, better warn
- # the user
- add_signature_headers(m, [], 'no signature found')
else:
# 'Combined method', the signatures are returned
# by the decrypt_verify function.