GnuPG Made Easy. http://git.bktus.com/gpgfrontend/gpgme/atom?h=tobias%2Ffix-proc-all-sigs-gpgtar 2024-10-04T11:39:17Z 2024-10-04T11:39:17Z Tobias Fella tobias.fella@gnupg.com 2024-10-04T11:17:11Z urn:sha1:4541fe94fe194a40630cb76c0d8305da62f9dc09 Currently, the flag is getting passed to gpgtar directly, which doesn't know about the flag and exits. Instead, prepend a "--gpg-args" to the parameter so that gpgtar passes it to gpg GnuPG-Bug-ID: 7320 2024-09-26T09:18:56Z Werner Koch wk@gnupg.org 2024-09-26T09:18:56Z urn:sha1:3bf1ea97bcabac31d29f17320cdad2f75f759435 * src/engine-gpg.c (gpg_addadsk): Extend the version check. 2024-09-20T08:05:30Z Ingo Klöcker dev@ingo-kloecker.de 2024-09-20T08:05:30Z urn:sha1:79ca846993638de359936f86eafaa23f75c9f85d src/encrypt-sign.c (encrypt_sym_status_handler): Add call of _gpgme_encrypt_status_handler. (encrypt_sign_start): Call _gpgme_op_encrypt_init_result with success_required=1 if archive is created. Always call _gpgme_op_sign_init_result with success_required=0 because the encrypt status handler already checks for SUCCESS. src/encrypt.c (op_data_t): Add success_seen flag. (_gpgme_encrypt_status_handler): Return error if we didn't see a required SUCCESS on GPGME_STATUS_EOF. Set success_seen flag on GPGME_STATUS_SUCCESS. (encrypt_sym_status_handler): Add call of _gpgme_encrypt_status_handler. (_gpgme_op_encrypt_init_result): Add argument success_required. Set success_seen flag if SUCCESS is not required. (encrypt_start): Call _gpgme_op_encrypt_init_result with success_required=1 if archive is created. src/ops.h (_gpgme_op_sign_init_result, _gpgme_op_encrypt_init_result): Add argument success_required to prototypes. src/sign.c (op_data_t): Add success_seen flag. (_gpgme_sign_status_handler): Return error if we didn't see a required SUCCESS on GPGME_STATUS_EOF. Set success_seen flag on GPGME_STATUS_SUCCESS. (sign_init_result): Add argument success_required. Set success_seen flag if SUCCESS is not required. (_gpgme_op_sign_init_result): Add argument success_required and forward it to sign_init_result. (sign_start): Call sign_init_result with success_required=1 if archive is created. -- gpgtar emits a SUCCESS status just before successful termination. If the process terminates unexpectedly (e.g. because it's killed) then gpgme now reports GPG_ERR_EOF. The SUCCESS status is only required if a signed and/or encrypted archive is created which is only supported for OpenPGP. The other engines reject the GPGME_ENCRYPT_ARCHIVE flag so that we don't need to check the protocol in the generic code. This change also adds handling of invalid recipients in case symmetric encryption is used which makes sense because one can combine symmetric and public key encryption. GnuPG-bug-id: 6554 2024-09-17T13:11:12Z Ingo Klöcker dev@ingo-kloecker.de 2024-09-17T13:11:12Z urn:sha1:9747f189620a4c89f88f50c5960baa511eea0a97 * configure.ac: Look for yat2m first in $prefix/bin and then in $PATH. -- This makes sure that yat2m is found in case libgpg-error and gpgme are installed in the same prefix. 2024-09-17T12:30:57Z Ingo Klöcker dev@ingo-kloecker.de 2024-09-17T12:30:57Z urn:sha1:e4b04ae15363ee8b2159dbc2586fbf93792598f6 * configure.ac: Add hint for YAT2M variable. Set HAVE_YAT2M if yat2m was found. * doc/Makefile.am (myman_pages): Set to empty string if yat2m isn't available -- 2024-09-10T14:58:29Z Sébastien Noel sebastien@twolife.be 2024-09-10T14:43:58Z urn:sha1:8e7f443045f8e77bb5c841c2b7bfe2e1e3fcceb9 * doc/gpgme-json.texi: New. * configure.ac: Check for yat2m. * doc/Makefile.am (YAT2M_OPTIONS): New. Also add all the other man page stuff similar to what is used in gnupg. -- ChangeLog entries by wk. 2024-09-10T14:38:18Z Werner Koch wk@gnupg.org 2024-09-10T14:38:18Z urn:sha1:09b694359ff5dadc8db205597829c09c9c7af9d0 -- Fixes-commit: 7e7eaf43424556c3c25edc7b67e760ab60de55ce 2024-09-09T15:33:29Z Werner Koch wk@gnupg.org 2024-09-09T15:33:29Z urn:sha1:cd79fc39736fda6ce38f1f79700cf658c47372f9 * src/gpgme.h.in (GPGME_ENCRYPT_ADD_RECP, GPGME_ENCRYPT_CHG_RECP): New flag values. * src/engine-gpg.c (have_cmd_modify_recipients): New. (gpg_encrypt): Check availability of the feature and prepare command. * tests/run-encrypt.c (main): New options --add-recipients and --change-recipients. -- GnuPG-bug-id: 1825 2024-09-04T12:31:12Z Ingo Klöcker dev@ingo-kloecker.de 2024-09-04T12:31:12Z urn:sha1:2264b64b85e6d522fdc5e06d5260f5b7b5414417 * src/key.c (_gpgme_key_append_name): Support email-only user IDs with upper case letters. * tests/gpg/t-keylist.c (struct key_info_s): Add algo, length, sec_algo, sec_length. (keys): Add expected algo and length for primary and secondary subkeys. (main): Factor out code for checking a key and the code for the keylist test. Call the factored out test function and a new test function. (check_key, test_keylist, key_with_email_only_user_id, key_info_email_only_user_id, test_email_only_user_id_with_upper_case_letters): New. -- Email-only user IDs with upper case letters are now also parsed as a user ID with empty name and the complete user ID as email. GnuPG-bug-id: 7280 2024-09-02T13:33:25Z Ingo Klöcker dev@ingo-kloecker.de 2024-09-02T13:33:25Z urn:sha1:ecd0c86d62351d267bdc9566286c532a394c711b * lang/python/setup.py.in (BuildExtFirstHack.run): Extend members of the extension instead of lists that were passed to the extension. -- setuptools 72.2.0 integrated changes in distutils which included "Support for Pathlike objects in data files and extensions". With this change the extensions now take a copy of the sources list passed to the constructor instead of keeping a reference to the passed list. Hence, modifying the sources list that was passed to the extension didn't change the sources list of the extension anymore. This is fixed by modifying the sources list of the extension directly. For consistency we do the same for the swig_opts list. GnuPG-bug-id: 7281