I notices this again, even though my display language is german and Kleopatra is german the GnuPG system is using english (gpg-error --locale says en_IE). en_IE was set by virtualbox during windows installation. No environment variables are set related to language.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 31 2024
I've checked the windows configuration and the automatic update of root certificates is not switched off.
Looking into the windows events view I did not see the certificate update, but after a while I did (restarts, edge attempts installation of firefox). So probably the edge view may have triggered this update, but it did not show directly in the cert store and thus not for Gnupg.
next I'll turn up dirmngr's logging
Since only https fails for you.
Jul 30 2024
Hi Bernhard,
Jul 27 2024
That fixed it.
Jul 22 2024
Uhm this is a task I have with High priority. I do not know what to do here or what it is really about. -> Invalid.
Jul 19 2024
Jul 10 2024
No next work item here. So resolved.
As there does not seem to be a problem here anymore -> Resolved.
I don't think this ticket is up to date. Especially since we now have more components. Auto update or Microsoft Store integration would be much more important then a single click installer.
Jul 9 2024
are there any news about the problem with the control file?
Jul 4 2024
Jun 17 2024
Jun 5 2024
Jun 4 2024
works, tested with Gpg4win-4.3.2-beta23
May 7 2024
Was anything done here apart from en-/decoding filenames to/from UTF-8 on Windows?
Apr 30 2024
Apr 24 2024
Apr 16 2024
What is the current status of this issue?
Apr 9 2024
This was done by Tobias.
Apr 5 2024
Apr 3 2024
Sorry, I did not know (or had forgotten, I did search the tracker first).
What is the rationale for not signing the uninstallers?
This is long known and we won't fix this for gpg4win.
With Gpg4win-4.3.1 I consider this solved:
Apr 2 2024
Mar 27 2024
FYI as a VSD customer you have access to support. Please check Help-> about Kleopatra for the infos,
In a current version I see this at least if I do not quit Kleopatra completely and restart to another screen setting. Further testing at the moment is not warranted, as there will be changes to the columns handling with the switch to Qt6. (T6924)
Btw compare the Kleopatra versions in Gpg4win and your VSD Version. They should mostly be identical with VSD maybe lagging a bit behind, Or your emplayer has not updated VSD. Many don't
I assume you mean the information shown in the subkeys window int the column "Strength"?
Mar 22 2024
Mar 13 2024
Mar 11 2024
Mar 10 2024
There is no way to recover it?
Sorry, this is not a help line but a bug tracker. If you lost or forgot your password you are screwed up.
Mar 9 2024
Feb 28 2024
Feb 25 2024
Thanks for the rort
Feb 22 2024
This is just another sympton with the same root cause. Therefore I have closed this as duplicate.
Interesting. I didn't even know that this feature exists.
I already mentioned the exact same thing in T7004 and this user also used the wiki style of the bug report form at first to report a bug. That is why I took the extraordinary step of blocking him.
Feb 21 2024
Closing due to age and because gpg4win 4 started to using the much improved GnuPG 2.4
Way to old. Does anyone still uses CAcert?
Please note that this is a bug tracker and not a general support channel. You would also need to write in English - we can't triage reports written in other languages.
Too similar to T7004 I have disabled this user.
Feb 20 2024
@jmrexach I think I undestand now @TobiasFella can you have a look please?
Hi,
please use English in this tracker. At least using an online translation service.
Je n'arrive pas importer clef d'un vendeur sans avoir cette erreur :
Une erreur s'est produite lors de la tentative d'exportation des certificats OpenPGP.
La commande
C:\Program Files (x86)\GnuPG\bin\gpg.exe a renvoyé : gpg: envoi de la clef ED607E44BAC58B1D à hkps://keyserver.ubuntu.com gpg: échec d'envoi vers le serveur de clefs : Server indicated a failure gpg: échec d'envoi vers le serveur de clefs : Server indicated a failure
Hi,
To reproduce this just change an item in the filter list: The contents of the window changes but NOT the name (title) of the window (only in the leftmost tab).
I cannot reproduce this. If I right click the tab I can rename it just like every other tab. The tabs do not change their names based on the current filter that is used that is only their default name. And the default for the first Tab is "All Certificates"
Feb 19 2024
Feb 15 2024
Seems to be a small problem with the regex used for extracting the gpg4win version number from kleopatra's version number. See https://invent.kde.org/pim/kleopatra/-/merge_requests/117/ for fix and details.
Talked to werner about this. We will but the list of signed files into the Gpg4win repo proper to that signing is part of the normal Gpg4win release (of course only if you have a signing key configured)'
Quick hint how to test a fix given that the versions.gnupg.org currently does not carry an entry for gpg4win.
Feb 14 2024
Yeah I also signed all the binaries for the last Gpg4win release (4.2.0). I think we should support the case that only signed binaries are allowed on a system.
I guess that's what it is called. A person in the forum told that GpgOL could not be loaded in Outlook and saw that the signature is missing in the new version. But it was there in version 4.2.0. With the command Get-AuthenticodeSignature I could confirm that this is the case.
You mean the Authenticode signature? Afaics, only the gnupg files come with such signatures.
I have disabled update notifications for now. We can reenable them with the next Gpg4win release when we fix Kleopatra to again query for the Gpg4win version and not for the Kleopatra version. I am leaving this open to fix just that in Kleopatra. If you now go under help -> check for updates it won't show you an update anymore.
Will do. Thank you very much.
Feb 13 2024
You have to restart once. Then it goes away. We can't do much about this since we load the icons etc. at startup and don't have dynamic color changing. It might be better with the next Version which will update our UI Framework but no promises. I leave it open for now so that is a known issue.
Ikloeker is our resident accessibility expert and Kleopatra has a certificate for accessible software so I agree that we should not change it. Or is there a specific issue / condition for you that makes this extra hard to read?
For accessibility the contrast between text and background must be high. Therefore, I don't think we should change the color. In any case, you get what you asked for: A dark (green) background color.
I need to investigate why this happens. Maybe we can as a workaround fix it on our server side without the need for a new update.