<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/python, branch gsoc/jacob-key-import</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gsoc%2Fjacob-key-import</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gsoc%2Fjacob-key-import'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-06-17T04:35:20Z</updated>
<entry>
<title>python bindings: core - key import</title>
<updated>2018-06-17T04:35:20Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-17T04:35:20Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=5a80e755008bbb3f4c7f91ffccd38f26cd8b3960'/>
<id>urn:sha1:5a80e755008bbb3f4c7f91ffccd38f26cd8b3960</id>
<content type='text'>
* Wrapped the key import function in the try/exception statements
  needed to catch at least the most likely unsuccessful import attempt
  errors.
* Mostly draws on the file error and no data import statuses for
  errors, with a couple of exceptions.

Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>python bindings: core key import</title>
<updated>2018-06-16T23:28:30Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-16T23:28:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=0e762608ef5a598030b8d0e56261a830e1b7b724'/>
<id>urn:sha1:0e762608ef5a598030b8d0e56261a830e1b7b724</id>
<content type='text'>
* The foundation of a pythonic key import function authored by Jacob
  Adams.
* A unit testing script for the same function originally authored by
  Tobias Mueller
* Added DCO reference for Jacob Adams to the GPGME AUTHORS file.
* Additional details regarding this patch are available here:
  https://dev.gnupg.org/T4001

Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>script: groups.py</title>
<updated>2018-06-10T15:03:58Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-10T15:03:58Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=92cd060f5e2f4fdbfbe4812ebe8ef57e82e1609f'/>
<id>urn:sha1:92cd060f5e2f4fdbfbe4812ebe8ef57e82e1609f</id>
<content type='text'>
* Added check for if it is run on a Windows system so that the correct
  binary filename is invoked.
</content>
</entry>
<entry>
<title>examples: python howto</title>
<updated>2018-06-07T05:06:20Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-07T05:06:20Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a3a08584d6e57c4b2a40d74dc52a7d8c5c11b501'/>
<id>urn:sha1:a3a08584d6e57c4b2a40d74dc52a7d8c5c11b501</id>
<content type='text'>
* 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.
</content>
</entry>
<entry>
<title>docs: python bindings howto</title>
<updated>2018-06-02T14:46:46Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-06-02T14:46:46Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=897423422b9d3b856bfb72fbe1995b91d153a54e'/>
<id>urn:sha1:897423422b9d3b856bfb72fbe1995b91d153a54e</id>
<content type='text'>
* Another attempt at fixing the org-mode version.
* A proof reader ascertained there were tabs in it instead of whitespace.
* Stripped the lot out and replaced with standard 4 spaces, fixed
  every incorrect example ... and it still breaks upon save and/or export.
* Added the reference to the mutt-groups.py script to demonstrate the
  groups.py module/code.
</content>
</entry>
<entry>
<title>examples: mutt crypt-hooks generator</title>
<updated>2018-05-24T21:12:52Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-05-24T21:12:52Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=321005c12f716814d86e139eb265437bda01380f'/>
<id>urn:sha1:321005c12f716814d86e139eb265437bda01380f</id>
<content type='text'>
* 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).
</content>
</entry>
<entry>
<title>docs: python bindings howto</title>
<updated>2018-05-24T19:50:11Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-05-24T19:22:16Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=48e946a96d05effd56b34761b98eebb6b2a6fae1'/>
<id>urn:sha1:48e946a96d05effd56b34761b98eebb6b2a6fae1</id>
<content type='text'>
* 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.
</content>
</entry>
<entry>
<title>doc: python bindings howto</title>
<updated>2018-05-24T19:50:11Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-05-13T18:14:45Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=9038d30017b2e38b183d093f9b5d46e1f24c70a6'/>
<id>urn:sha1:9038d30017b2e38b183d093f9b5d46e1f24c70a6</id>
<content type='text'>
* Fixed org-mode python source indenting.
** Note: nested indented blocks do not indent correctly when exported
   to [X]HTML.
</content>
</entry>
<entry>
<title>docs and examples: python howto</title>
<updated>2018-05-23T04:43:06Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-05-23T04:43:06Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=3a9e6a8e088e233097866bb0560a36cfbbc4470e'/>
<id>urn:sha1:3a9e6a8e088e233097866bb0560a36cfbbc4470e</id>
<content type='text'>
* 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.
</content>
</entry>
<entry>
<title>python: key expiration datetime stamp tests</title>
<updated>2018-05-05T02:27:17Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-05-05T02:27:17Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=46da79e3de99a7b65748994921d6aab73b9974e7'/>
<id>urn:sha1:46da79e3de99a7b65748994921d6aab73b9974e7</id>
<content type='text'>
* Changed the expiration date for the generated test key to NYE this
  century, rather than the NYE this millennium as originally suggested
  in job #3815.
* This covers the lifetimes of current users (except, maybe, some very
  healthy millennials) as well as the 32-bit clock end date in 2038;
  without falling foul of OpenPGP's 2106 expiration.
</content>
</entry>
</feed>
