gpgme, branch ben/howto-update-05GnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Fhowto-update-052018-05-29T23:11:28Zexamples: exporting keys2018-05-29T23:11:28ZBen McGinnesben@adversary.org2018-05-29T23:11:28Zurn:sha1:fd4226429d923537ad5a04141163fdb5ee7c04db
* Fixed the descriptions and explanation of what happens if no
search/user ID/key ID data is included (it exports the lot).
examples: python bindings2018-05-29T22:55:12ZBen McGinnesben@adversary.org2018-05-29T22:55:12Zurn:sha1:93bdf4b50aca884859125d041685e0b2cfe2b4fe
* 2 more scripts for planned expansion of the HOWTO.
* export-key.py - is very similar to both the import-key.py script and
an earlier example.
* export-secret-key.py - the holiest of holies, a script to be very
careful with (though on posix systems it is saved in a chmodded 600
file).
examples: python bindings howto2018-05-25T12:59:17ZBen McGinnesben@adversary.org2018-05-25T12:59:17Zurn:sha1:095093df2037fa5fc2778fa5fac13a5d2d73e8dd
* Added a script for planned HOWTO expansion demonstrating key import
from a file with optional alternative homedir setting.
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.
doc: python bindings howto2018-05-24T19:50:11ZBen McGinnesben@adversary.org2018-05-13T18:14:45Zurn:sha1:9038d30017b2e38b183d093f9b5d46e1f24c70a6
* Fixed org-mode python source indenting.
** Note: nested indented blocks do not indent correctly when exported
to [X]HTML.
json: Add code to gpg_error based messages2018-05-24T14:35:42ZAndre Heineckeaheinecke@intevation.de2018-05-24T14:35:42Zurn:sha1:9fca7c84067c0d4c968c8920dc8ef9449769c5ea
* src/gpgme-json.c (gpg_error_object): New.
(error_object_v): Extend to take error.
--
Having the error code is helpful, especially as
the strerrors are localized. E.g. to detect
an ERROR_CANCELED.
json: Implement op_version2018-05-24T14:15:14ZAndre Heineckeaheinecke@intevation.de2018-05-24T14:15:14Zurn:sha1:61f4532ba979dea1acd8c7de9b7d56bb8ff552d5
* src/gpgme-json.c (op_version): New.
(process_request): Extend for version.
(protocol_to_string, add_ei_to_object): New helpers.
json: Implement op_verify2018-05-24T14:14:54ZAndre Heineckeaheinecke@intevation.de2018-05-24T11:56:16Zurn:sha1:5fbf81c18b277b30639ba09e8c5d21573b444b00
* src/gpgme-json.c (op_verify): New.
(hlp_help): Add verify.
(process_request): Add verify.
--
Mostly works, except for detached, base64 encoded signatures,
they are somehow not yet written to gpgme.
json: Put signature info before data output2018-05-24T11:36:31ZAndre Heineckeaheinecke@intevation.de2018-05-24T11:36:31Zurn:sha1:c679ed24778c997fee72d3613babad8680855882
* src/gpgme-json.c (op_decrypt): Move info before data.
--
This should enable it to first parse signatures before
handling very large chunks of data.