diff --git a/lang/python/docs/dita/gpgme-python-howto-footer.xhtml b/lang/python/docs/dita/gpgme-python-howto-footer.xhtml new file mode 100644 index 00000000..77d681a1 --- /dev/null +++ b/lang/python/docs/dita/gpgme-python-howto-footer.xhtml @@ -0,0 +1,9 @@ + + +
+Unlike all other documentation in the
This was done for two main reasons:
The XML format definitely supports displaying all the more complex Python code correctly, - as well as being designed to produce standards compliant print and HTML output. Whereas - currently the existing tools utilised by the GnuPG Project can't display the example code in - a way which would actually pass the project's own git commit ruleset.
+The XML format definitely supports displaying all the more complex Python code correctly + with syntax highlighting, as well as being designed to produce standards compliant print and + HTML output. Whereas currently the existing tools utilised by the GnuPG Project can't + display the example code in a way which would actually pass the project's own git commit + ruleset.
There are two methods of exporting public keys, both of which are very similar to the
+ other. The default method,
+
It is important to note that the
+
Exporting secret keys is, functionally, very similar to exporting public keys; save for the
+ invocation of
The following example exports the secret key to a file which is then set with the same + permissions as the output files created by the command line secret key export options.
+
+
Alternatively the approach of the following script can be used. This longer example saves
+ the exported secret key(s) in files in the GnuPG home directory, in addition to setting the
+ file permissions as only readable and writable by the user. It also exports the secret
+ key(s) twice in order to output both GPG binary (
+
Exporting keys remains a reasonably simple task, but has been separated into three + different functions for the OpenPGP cryptographic engine. Two of those functions are for + exporting public keys and the third is for exporting secret keys.
+ +Importing keys is possible with the
The following example retrieves one or more keys from the SKS keyservers via the web using + the requests module. Since requests returns the content as a bytes literal object, we can + then use that directly to import the resulting data into our keybox.
+
+
+
Decrypting something encrypted to a key in one's secret keyring is fairly straight forward.
In this example code, however, preconfiguring either
The data available in
The data available in
+
There is not yet an easy way to access groups configured in the
The following code, however, provides a work-around for obtaining this information in Python.
The result of that code is that
The
To use this code as a module use:
A demonstration of using the
Version: 0.1.1
+Version: 0.1.2-DRAFT
Author: Ben McGinnes <
Author GPG Key ID: DB4724E6FA4286C92B4E55C4321E4E2373590E5D
+Author GPG Key ID:
+
Language: Australian English, British English