- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 16 2022
Applied to 1.10 branch.
didn't seem to work with 1.9.x
Closing as I believe this is a downstream bug.
Jun 15 2022
Please read at least one article that explains how to write a good bug report. I'm pretty sure that you will find plenty of good articles using your favorite search engine.
Thanks! Interestingly didn't seem to work with 1.9.x but it does with 1.10x. Maybe I made some error when testing.
In the branch https://dev.gnupg.org/source/Scute/history/t6002/ , by the commit rS123d617ebefe: Less administration of devices by scute., things has been changed.
Jun 14 2022
When I replied to the bug report I had the very same idea. Thanks for adding.
Here is a test signature with long notation data. During verification gpg faults when emitting the NOTATION_DATA lines.
As Werner wrote, this is already possible. The next time please consult the extensive documentation of gpgme before opening a ticket.
Thank you. Applied.
ntbtls support only 1.2. We can't disable cipher suites for interop reasons. It is not the client's job trying to force a server 's admin to offer only decent ciphersuites.
Jun 13 2022
Hmm, why not use:
gpgme_op_sign (ctx, in, out GPGME_SIG_MODE_CLEAR)
The buttons in the main toolbar can now be selected with Tab and Shift+Tab.
The original description of the problem seems to be wrong. gpg-agent does not have a KEYPARAM command. If I understand correctly then gpg-agent sends a KEYPARAM inquiry to the client, but you are sending KEYPARAM to the server.
I realized that we need to invent a way to represent KEYGRIP (40-byte string) in the scheme of PKCS#11; PKCS#11 uses fixed-size string (space padded) for it's label (32) and serialno (16). Basically, it identifies the device by slot number.
Jun 12 2022
Patch applied to master with small changes.
Jun 11 2022
FWIW, on Unix is common to describe options as given on the standard shell.
Jun 10 2022
The quotes are irrelevant because they are evaluated by the shell and don't make a difference here.
You need to install the correct Let's Encrypt CA certificates on your legacy Windows box. Check the mailing lists for a discussion on this topic.
No crash here
Duplicate of T6021. Please don't create a new bug for one you already created (and which was marked as won'tfix).
Added missing context lines and replaced some tabs with spaces