- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Thanks Ingo. It seems 2.5.17 is not too far away.
I can reproduce this on the command line:
C:\Users\g10code>"c:\Program Files\GnuPG\bin\gpgsm.exe" --export --armor 579BAF3DF16AD462457BCC0897ADBC143D76EA7B 5A2B80F98F518D50891B1F0C7C6131AD107F9938 DB625D2BBBB5A3FD985C0233249B03090E85D402
Issuer ...: /CN=CA IVBB Deutsche Telekom AG 20/OU=Bund/O=PKI-1-Verwaltung/C=DE
Serial ...: 02195D190EBE34
Subject ..: /CN=iOS Test-Smartcard iostest01.sc/OU=BSI/O=Bund/C=DE/SerialNumber=2
aka ..: iostest01.sc@bsi.bund.de
Keygrip ..: 527CE32FD0552D18479442EF90DD5E434C036329I can reproduce the issue only (!!!) with keyboxd (on Windows).
Yesterday
implemented TypeScript workflows using tsc without vite
Sat, Jan 10
Fri, Jan 9
So w/o the new option we have:
Thanks Werner.
I updated the rendered form of the English GPH with a warning and a link to the blog.
Thanks for the hint.
The behaviour might have changed a bit because of the ldap: prefix i use now, or i have missed this case the last time:
Given some cert on the "download" server, I can find it, if dirmngr.conf contains only the "download" server, or if the "download" server is listed first:
Will be in the next release.
testing will wait for special build
it does not make sense to have a workboard item for this parent ticket.
Independent of keyserver order in dirmngr.conf, --search-keys still offers keys from the upload server, but the download fails:
For "Although the upload server is used for upload, the gpg message still displays the first keyserver" see T8025
I am using that version and key daily. No problems seen.
Looks good to me on gpg4win-5.0.0-beta479 @ win11:
was tested already by timegrid
This does not happen any more, tested with Gpg4win-5.0.0-beta479
Tested with Gpg4win-5.0.0-beta479
in Gpg4win-5.0.0-beta479
Looks good to me on gpg4win-5.0.0-beta479 @ win11:
with Gpg4win-5.0.0-beta479 the listing after creating the new key with ADSK looks ok now:
I think we won't fix that for 2.2
I assume, that testing the functionality is the only thing I can do here.
That was also fixed in gnupg 2.2.50 and thus vsd 3.3.3
That was fixed with 2.2.52 which fixed a bug in the fix done in 2.2.50 (see rG31fef13df1). Note that 2.2.48 to 2.2.50 had only internal releases.
Given that the 2.2 fix has been tested and resolved and we don't have another ticket for 2.6, we can close this one.
Looks good to me on gpg4win-5.0.0-beta479 @ win11
Okay, let's backport this.
Note that for exploiting this bug a second preimage attack for SHA-1 is required. This kind of attack on SHA1 is not yet possible.