- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 26 2024
Nov 25 2024
Well, T6893 was removed from this release, at least for the windows builds, therefore this ticket can not be tested on windows for vsd33
The certificates are shown
Yes, much improved, changes as described in https://dev.gnupg.org/T6933#181791
tested with Gpg4win-Beta-75++
I cherry picked your patch for master and 2.4.
For this ticket, I reviewed the code around my SOS changes.
Because I'd like to focus the point of retaining binary representation when doing import->export,
I created another thicket: T7426
Actually, it's a bug when importing a key. It's not-intended-side-effect of the change in rG0a5a854510fd: gpg: Fix false negatives in Ed25519 signature verification..
Fixed in rG70c49ce02401: gpg: Fix modifying signature data by pk_verify for Ed25519.
Nov 24 2024
Nov 23 2024
Nov 22 2024
For master fixed with rGbb6b38c24010258c7cb2da840d0a088fe43393b3 (Wrong bug id used).
Also fixed for gnupg24.
Gpg4win-Beta-75++
Gpg4win-Beta-75++
Checked with Gpg4win-Beta-75++
It works, technically.
But for this to work you have to put the keyword "qual" at the end of the line of the system trustlist.txt file, the user trustlist.txt won't work. Example line:
Nov 21 2024
Cancelling the password window works know.
Should probably be backported for VSD 3.3 because very likely this happens always when a new PKCS#15 card (with unknown certificates) is inserted. Workaround: Close and re-open the smart card window.
With gpg4win-beta-75++ tryiing to import a secret key results in no import:
Error on generate keys on card is now: "Failed to generate new card keys and a certificate: Wrong PIN"