gpgme/lang/python/examples/howto, branch gsoc/jacob-key-importGnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=gsoc%2Fjacob-key-import2018-06-10T15:03:58Zscript: groups.py2018-06-10T15:03:58ZBen McGinnesben@adversary.org2018-06-10T15:03:58Zurn:sha1:92cd060f5e2f4fdbfbe4812ebe8ef57e82e1609f
* Added check for if it is run on a Windows system so that the correct
binary filename is invoked.
examples: python howto2018-06-07T05:06:20ZBen McGinnesben@adversary.org2018-06-07T05:06:20Zurn:sha1:a3a08584d6e57c4b2a40d74dc52a7d8c5c11b501
* Uses the groups module to prepare a list of recipients and encrypt
to those.
* The main version (encrypt-to-group.py) tries to check for invalid
recipients, but still falls back to always trust for the second
encryption attempt.
* The gullible version doesn't try pruning the recipient list at all,
it just tries to encrypt and if it fails, switches straight to
always trust.
* The trustno1 version doesn't use the always trust model at all and
only attempts pruning the list of invalid recipients.
examples: mutt crypt-hooks generator2018-05-24T21:12:52ZBen McGinnesben@adversary.org2018-05-24T21:12:52Zurn:sha1:321005c12f716814d86e139eb265437bda01380f
* Added a script which demonstrates how the groups module works.
* Script generates Mutt/Neomutt crypt-hooks for every group entry in
gpg.conf, including those entries for multiple keys (Mutt handles
that differently).
docs: python bindings howto2018-05-24T19:50:11ZBen McGinnesben@adversary.org2018-05-24T19:22:16Zurn:sha1:48e946a96d05effd56b34761b98eebb6b2a6fae1
* Fixed the groups.py script so it really does what is described (the
old code had the same result for groups, group_lines and
group_lists).
* Updated the corresponding example in the doc to match.
docs and examples: python howto2018-05-23T04:43:06ZBen McGinnesben@adversary.org2018-05-23T04:43:06Zurn:sha1:3a9e6a8e088e233097866bb0560a36cfbbc4470e
* Updated the decryption example code in the HOWTO and the
corresponding decrypt-file.py script to gracefully handle a
decryption failure. This error will always be triggered when GPGME
is used to try to decrypt an old, MDC-less encrypted message or
file.
example: revoke UID2018-03-28T23:21:52ZBen McGinnesben@adversary.org2018-03-28T23:21:52Zurn:sha1:3b91f6af378ccc37dcf8924cbc157894c35b5192
* Script to revoke a UID on an existing key.
example: key signing2018-03-28T22:49:08ZBen McGinnesben@adversary.org2018-03-28T22:49:08Zurn:sha1:56bbfd39acea90eb87a28b11a515b0314cdda54c
* Added script for signing or certifying keys.
example: add user ID2018-03-28T19:36:14ZBen McGinnesben@adversary.org2018-03-28T19:36:14Zurn:sha1:5cd419341807d8ae23fec7bd9bb7025a8a2dcb3c
* Added script to add a UID to an existing key.
example: key creation2018-03-27T01:29:08ZBen McGinnesben@adversary.org2018-03-27T01:29:08Zurn:sha1:f9159b1d75d3209b1c22bbb0ed4472800b60a522
* Script to generate a new key with encryption subkey taking input
from interactive prompts.
* Will also take a passphrase via pinentry and uses passphrase caching
of five minutes when used in conjunction with the temp homedir
script.
script: temp homedir config2018-03-27T01:16:29ZBen McGinnesben@adversary.org2018-03-27T01:16:29Zurn:sha1:1b5da37a47ceef41545e0b2474738613f36be949
* added passphrase caching of 5 minutes.