Yesterday
@uwi: We removed the ciphersuite from the server and tested with 4.2.0 that you get an update notification now. Because of some caching you may need to
This is due to an update of the server providing the version info. The server (Apache) uses a smaller hash than the ECC key. This is allowed behaviour and was fixed in our TLS library in 2022; see T6059. However, the new library was released only early this year an. We will check whether we can tell our Apache to use a more correct hash algorithm.
Ok. Sorry, just to avoid debugging in case it is not known, I am pretty sure the ini file is a regression from the unicode nsis switich. The timing when it was reported to no longer work matches around that time and the installer code itself hasnt changed for even longer.
Thu, Dec 12
Thanks for the clarification, it seems that was necessary.
Jut a note (in case it was not clear enough): I was *not* talking about registering "*.pub" for Kleopatra (currently it launches Microsoft Publisher), but I was talking about the file selector's default input pattern (I had to switch to "all files" to be able to see the file I wanted to import):
Wed, Dec 11
- name: Uninstall gpg4win from the registry ansible.windows.win_package: product_id: 'Gpg4win' arguments: /S state: absent
From a quick glance at the docs. This looks completely correct. What did this do and what didn't it do?
Just to explain, if you are executing it from the command line the command line will "lock" the uninstaller until it is finished. In GUI Mode it creates a copy in %TEMP% launches this copy and exits. When run from the command line it requires a session reset to delete the unistaller. So log out / log in and the uninstaller should be removed, but the dir might still exist. I am not sure. To workaround you need to copy the uninstaller to a temporary locationm firs and then execute and delete the copy.
I wasnt aware of this either, but it would be good since we currently don't have a file extension listed explicitly for pgp keys, even though we register one and have the strings already to handle downloading keys where the server transfers application/pgp-keys as information. While https://support.microsoft.com/en-us/windows/common-file-name-extensions-in-windows-da4a4430-8e76-89c5-59f7-1cdbbc75cb01 recognizes it as Microsoft Publisher file wikipedia says PGP Public key but without a citation. If AllowSilentDefaultTakeover is not set, the following code will not automatically change .pub to kleopatra. Instead in microsoft publisher is installed, it will ask you for the first time when a .pub file is opened after installing Kleopatra if you want to keep opening the files with Microsoft Publisher or if they should be opened from now on with IKleopatra,.
Also fixed for 2.4. Don't use the uninstaller on the command line, you should use the Windows method to do this.
Fixed with rG4c830b240c for gpd5 but after the release. Will fix it for 2.4 too.
Really. I do this for PGP files but I have not seen that elsewhere.
Not sure about gpg4win 4.2.0 but we had a bug in 4.3.0 which has been resolved with T6985
Closing since the cause for this was identified.
Fri, Dec 6
tested with Gpg4win 4.4
Mon, Dec 2
Gpg4win 4.4.0 has just been released. Creation of encrypted archives has been completely reworked with Gpg4win 4.3.0 already. I could create an encrypted archive containing the two files with GpgEX without problems.
Christoph refers to this post here:
https://forum.gnupg.org/t/readme-4-3-1-en-txt-currently-missing-from-files-gpg4win-org/5845/4
Gpg4win 4.4.0 has just been released. I cannot reproduce unexpected results when doing a lookup on server. Unfortunately, many keyservers do not publish the user IDs (i.e. name and/or email address) anymore. Kleopatra does not list results without user IDs because GnuPG won't import them anyway.
This has been fixed in the meantime. If you should still experience this problem with Gpg4win 4.4.0 then reopen this ticket.
Gpg4win 4.4.0 has just been released. I assume that this has been fixed in the meantime. In particular, "General error" should happen a lot less. If the problem still occurs with Gpg4win 4.4.0 then reopen the ticket.
This ticket is obsolete
This doesn't look like a problem in Kleopatra.
Kleopatra now let's gpg deal with I/O directly. This makes decryption with Kleopatra as fast (or slow) as with gpg on the command line. Hence I'll remove the Kleopatra tag.
Then please upload whatever README you want there. My release checklist does not mention any README.
Thu, Nov 28
Thu, Nov 21
tested with Gpg4win-Beta-75++
Nov 5 2024
If 7z is used to create a tarball that tarball is then 7z compressed. At least this is how I understand the case.
When gpgtar now tries to extract the file it sees a 7z file and thus emits the octal number warnings because it assumes a tarball (after decryption by gpg).
This problem was also reported at https://bugs.kde.org/show_bug.cgi?id=479567#c1
This ticket is obsolete, we did some work on gpgtar since then. Should the issue still occur, please reopen or create a new ticket
Oct 29 2024
Oct 9 2024
Yes, the fix is included in the Gpg4win 4.3.1.
Oct 8 2024
Was the fix part of a stable release? The beta was 4.2.1b55. Stable download on https://gpg4win.de/ is 4.3.1. Am I correctly assuming, that 4.3.1 includes the fix and this issue here can be closed?
This is a super old bug report, this is likely fixed with a new version of Kleopatra, so I am closing this. If this happen again in the future, feel free to reopen this bug report.
This is no longer possible. The sign/encrypt button is disabled and an info box is displayed.
No reply for a very long time, so I am closing this ticket. This is likely fixed now. Feel free to reopen if this happen again.
No reply for a very long time, let's close this.
gpg4win 4 has been released with unicode support. Closing.
Oct 4 2024
closing this ticket as duplicate as adding and changing expiry works.
Revocation of a single subkey is not yet possible in Kleopara, though