gpgme log for key creation and export with warning for VSD-Beta29
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Wed, Oct 29
This is also the case in the latest VSD-Beta29
I could reproduce it with the same version (on WIN10).
Right, gpg CLI output depends on it, too.
And when I switch of read-as-plain, both testmails in the inbox are displayed as expected but one of the ones from the sent-folder has an empty body:
Does that mean that it is not possible to close the message automatically if changes are made in a) the text field or b) the encryption settings in the right pane?
PS C:\Users\g10> gpg -K --with-colons sec:u:256:19:AFC0D3F82B25E93B:1761728062:1856426400::u:::scESCA:::D276000124010304000500009D590000::brainpoolP256r1:23::0: fpr:::::::::8501CB7EF858A7CFE5E1F6E4AFC0D3F82B25E93B: grp:::::::::2675ADEF564A96F12D6E5A9B29D4FB8FE0C6D741: uid:u::::1761728062::BE090A7B8780003B05D5F193AFF64BA827F1F05B::card::::::::::0: ssb:u:256:19:23FF18B366E41CFC:1761728062:1856426400:::::a:::D276000124010304000500009D590000::brainpoolP256r1:23: fpr:::::::::6EF74BF349E0E14886C521D323FF18B366E41CFC: grp:::::::::FD28C8EC5995AF83CFBEFA10A901745318C72D81: ssb:u:256:18:8D2D2E42DF4CD03A:1761728062:1856426400:::::e:::D276000124010304000500009D590000::brainpoolP256r1:23: fpr:::::::::7253B2F829C431CD4E0A5CE28D2D2E42DF4CD03A: grp:::::::::0459891236233D2D970E3B8A08EE662E1B5D9C42: sec:u:255:22:B889A166FB44BC68:1761727895:1856426400::u:::scESC:::+::ed25519:::0: fpr:::::::::F05E296612506679B40CC2EDB889A166FB44BC68: grp:::::::::50D88C2461B477037B39367E9AB262B8DDDFF0AE: uid:u::::1761727895::C1171D48754E1CC7C9A68E7C3D4B7951925F9A8D::Has ADSK::::::::::0: ssb:u:255:18:E8DAB91AEA053CCC:1761727895:1856426400:::::e:::+::cv25519:: fpr:::::::::50BB79B5B878C769F0973247E8DAB91AEA053CCC: grp:::::::::2B5EF50EC6A1797557F1543CE1198DE67BA9F675: ssb:u:256:18:8D2D2E42DF4CD03A:1761728062:1856426400:::::r:::D276000124010304000500009D590000::brainpoolP256r1:23: fpr:::::::::7253B2F829C431CD4E0A5CE28D2D2E42DF4CD03A: grp:::::::::0459891236233D2D970E3B8A08EE662E1B5D9C42:
with 3.3.90.29-Beta:
Please attach the output of gpg -K --with-colons
For the open issue I have created T7890: Kleopatra: Icon sidebar in configuration dialog is missing an accessible name because it needs to be fixed upstream (in KDE Frameworks).
Correct, the fix is not included in beta395.
For the initial attempt, I push: rCfe06287003a1: secmem: Handle HAVE_BROKEN_MLOCK for the case with ASAN.
This is better than nothing.
Tue, Oct 28
Notes to self:
- On Windows, libgpg-error's gettext replacement uses the value of LC_ALL, LC_MESSAGE, or LANG (in this order) if set. Otherwise, it uses Windows's GetThreadLocale. (gnupg should probably use the MUI API instead.)
- We should probably force Qt's/KDE's language on gnupg by setting LANG.
Please attach scdaemon logs (created with debug ipc,cardio)
I have no idea how Qt/KDE and how gettext (resp. gnupg's replacement of gettext for Windows) react to Windows's "regional format" setting. It seems that Qt/KDE correctly use English despite German regional format while gnupg uses German.
ZeitControl OpenPGP v3.4 card
Windows Language Settings:
- ISO: EnglishInternational
- Windows Language: English (United Kingdom) - note: i installed English (United States), but can't select it
- Country or Region: German
- Regional Format: German
The screenshots were made with
- ISO: EnglishInternational
- Windows Language: English (United Kingdom) - note: i installed English (United States), but can't select it
- Country or Region: German
- Regional Format: German
For such language tickets please give more information. What are your language settings? Not only in Kleo, the system language settings, too.
This works fine with my Yubikey. Maybe it's depends on the specific type of smartcard. What type of card are you using?
Mon, Oct 27
A side question: what are your language settings there?
Seems gpg gives it's error messages in German, Kleo in English
This can only be tested with the AppImage because on Windows we disable drag&drop of certificates.
- I might want to know the fingerprints of those unknown recipients to search for them (in the audit log I can't see, which of those fingerprints are unknown immediately)
Note that currently Kleopatra (gpg4win 5 beta) fails to delete the key, which might impact other operations. I'm currently trying to figure out, if some other bugs/quirks are a subsequent error or not.
Workaround is to use --with-keygrip and delete both <keygrip>.key files. Problem here is that one part may be on a smartcard or one part might be shared (although not allowed) with other keys.
there have been changes affecting this:
