From dda54cc851490be045832d5ee0b03be082529d17 Mon Sep 17 00:00:00 2001
From: Ben McGinnes
Date: Thu, 28 Jun 2018 18:02:43 +1000
Subject: python bindings howto: dita version
* Drafts of instructions for exporting public and secret keys ready,
along in addition to the code.
---
lang/python/docs/dita/howto/part04/decryption.dita | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
(limited to 'lang/python/docs/dita/howto/part04/decryption.dita')
diff --git a/lang/python/docs/dita/howto/part04/decryption.dita b/lang/python/docs/dita/howto/part04/decryption.dita
index 41a4650e..bb8c3680 100644
--- a/lang/python/docs/dita/howto/part04/decryption.dita
+++ b/lang/python/docs/dita/howto/part04/decryption.dita
@@ -30,9 +30,20 @@ else:
pass
- The data available in plaintext in this example is the decrypted content
- as a byte object, the recipient key IDs and algorithms in result and the
- results of verifying any signatures of the data in verify_result.
+ The data available in plaintext following a successful decryption in this
+ example is the decrypted content as a byte object, the recipient key IDs and algorithms in
+ result and the results of verifying any signatures of the data in
+ verify_result.
+
+ The graceful handling of GPGMEError with the try/except statement is
+ to handle the decryption error message produced if the file ciphertext,
+ and thus cfile, are encrypted with deprecated and insecure methods.
+ Particularly without MDC integrity checks or utilising deprecated encryption algorithms.
+ Messages and files encrypted with these are not decrypted with GPGME at all and any user
+ requiring archival access will need to access it manually with pre-GnuPG 2.3 versions of
+ the software which meets the requirements of the specific use case.
+
+