- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 4 2022
For unwrapping, it is good if we can support "automatic" unwrapping, apply W^-1 and check the first 8 octets to see if it's KW or KWP.
Thanks. Looks good to me (both merged changes and the above proposal). In addition to the changes proposed above, we certainly need to update the documentation about this, probably also the FSM diagram.
The problem was the error handling.
I didn't apply the patch directly, but improved the code paths.
And I'm testing following:
The "at first" change done.
At first, I think that we need to change the way how libgcrypt rejects non-approved cipher/md/mac/pk.
Jan 3 2022
We have full Unicode support on the command line since 2.2.28 (2021-06-10)
Jan 2 2022
Jan 1 2022
Dec 31 2021
Please review these changes
Dec 30 2021
Backport done but diligent testing is required.
Dec 28 2021
Unfortunately same story for GpgOL v42.5.1. Tried disabling all non-Microsoft plugins, however to no avail. Signed and encrypted messages are shown as blank, whereas I can see the content of the signed e-mails in the Outlook web client and on my iOS device.
Dec 24 2021
The new revision uses the python.m4 version from automake 1.16.5 and keeps Werner's modifications with the 4th parameter.
See also https://dev.gnupg.org/T3354 and https://dev.gnupg.org/rMff6ff616aea6f59b7f2ce1176492850ecdf3851e
I am not sure if you assumption about the intention is correct. After all, the openSUSE rpm build does use it for creating binding packages for all available python3 versions. If you remove the functionality to find all available versions ("flavors" in the openSUSE rpm packager lingo), the RPM build would need to introduce separate calls of configure and make.
Thank you for submitting the patch.
Dec 23 2021
https://bugs.kde.org/show_bug.cgi?id=447326
This problem also appears for trojita.
The debug log was from gpg and not from dirmngr and thus it is not helpful. I also guess that an older dirmngr was still running, because the LE bug has been fixed in 2.3.4.
Format sys.version_info[:2] instead of cutting it from sys.version[:3]
as Python versions >= 3.10 have more than 3 characters for their version
string. Bump minimum Python version to 2.1 because the new
ax_python_devel specifies this.
Will go into 2.3.4.