gpgme/src, branch javascript-binding

json: Put signature info before data output

2018-05-24T11:36:31Z

* 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 help

2018-05-24T11:31:15Z

* src/gpgme-json.c (hlp_help): Add sign.

json: Add op_sign

2018-05-24T11:29:23Z

* src/gpgme-json.c (op_sign): New.

json: Fix invalid function call

2018-05-24T11:16:55Z

* 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/verify

2018-05-24T10:37:29Z

* 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 fixes

2018-05-24T08:26:41Z

* src/gpgme-json.c: Minor typo fixes.

core, w32: Add w64 handling for regkeys

2018-05-17T15:46:12Z

* 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

core: Always fail if an OpenPG message is not integrity protected.

2018-05-17T07:16:05Z

* src/decrypt.c (struct op_data_t): Add field not_integrity_protected. (parse_decryption_info): Set this. Also rename mode to aead_algo for clarity. (_gpgme_decrypt_status_handler): Force failure in case of a missing MDC. -- This extra check makes sure that a missing or stripped MDC in - gpg < 2.1 - or gpg 2.2 with an old cipher algorithm will lead to a decryption failure. gpg 2.3 will always fail in this case. Implementing this check here and not backporting the 2.3 change to 2.2 has the benefit that all GPGME using applications are protected but scripts relying on rfc2440 (i.e. without MDC) will only break when migrating to 2.3. Note that S/MIME has no integrity protection mechanism but gpgsm neither emits a DECRYPTION_INFO status line, so an error will not be triggered. If in the future gpgsm supports authenticated encryption it may issue a DECRYPTION_INFO line to force a failure here but it will in that case also emit a DECRYPTION_FAILED anyway. GnuPG-bug-id: 3981 Signed-off-by: Werner Koch

json: Improve auto-base64 encoding to not split UTF-8 chars.

2018-05-09T14:41:05Z

* src/gpgme-json.c (make_data_object): Switch to Base64 also for UTF-8 characters. Signed-off-by: Werner Koch

core: Make the status-fd monitor work for all gpgsm commands.

2018-05-09T14:39:30Z

* src/engine-gpgsm.c (status_handler): Call the status monitor also here. Signed-off-by: Werner Koch