gpgme/src, branch ben/howto-update-05GnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Fhowto-update-052018-05-24T14:35:42Zjson: 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.
json: Add sign to help2018-05-24T11:31:15ZAndre Heineckeaheinecke@intevation.de2018-05-24T11:31:15Zurn:sha1:a6cd3a1197eb4efea0950394959c252f24475f67
* src/gpgme-json.c (hlp_help): Add sign.
json: Add op_sign2018-05-24T11:29:23ZAndre Heineckeaheinecke@intevation.de2018-05-24T11:24:02Zurn:sha1:1c0a55a60847563fecf92a383457ab3576aec5d8
* src/gpgme-json.c (op_sign): New.
json: Fix invalid function call2018-05-24T11:16:55ZAndre Heineckeaheinecke@intevation.de2018-05-24T11:16:55Zurn:sha1:b344933e4cb17f2f26c4ed355217428bda8b8c40
* src/gpgme-json.c (add_signatures_to_object): Fix call to
xjson_CreateArray.
--
That is what happens if you edit code while reviewing changes,
without testing it again,..
json: Print signatures for decrypt/verify2018-05-24T10:37:29ZAndre Heineckeaheinecke@intevation.de2018-05-24T10:34:31Zurn:sha1:45036c3c4c11f7bd56a00805564108e9377b657e
* gpgme-json.c (xJSON_CreateArray),
(add_summary_to_object, validity_to_string): New helpers.
(add_signature_to_object, add_signatures_to_object)
(add_signatures_object): New.
(op_decrypt): Handle verify_result.
(hlp_help): Mention decrypt.
json: Minor typo fixes2018-05-24T08:26:41ZAndre Heineckeaheinecke@intevation.de2018-05-24T08:26:41Zurn:sha1:fd5e14660a6f4eb1a89d69534e3e435f7fb05f8a
* src/gpgme-json.c: Minor typo fixes.
core, w32: Add w64 handling for regkeys2018-05-17T15:46:12ZAndre Heineckeaheinecke@intevation.de2018-05-17T15:41:53Zurn:sha1:e04b8142df21a49e6c4a3f8234cc14bfec217222
* src/w32-util.c (_gpgme_get_gpg_path): Use new defines.
(GNUPG_REGKEY_2): x64 aware regkey as used by GnuPG in Gpg4win 2.x
(GNUPG_REGKEY_3): x64 aware regkey as used by GnuPG in Gpg4win 3.x
(_gpgme_get_gpgconf_path): Use new regkeys. Add another fallback.
--
This should fix more "unsupported protocol" issues if Gpg4win /
GnuPG is installed in a non standard path on 64bit systems.
The regkey handling is similar to that of gpgex and gpgol.
GnuPG-Bug-Id: T3988