It seems to work here on Windows and Linux
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 12 2025
Note: Restoring the last window location is a built-in feature of KMainWindow/KXmlGuiWindow. It should work out-of-the-box if one makes sure that KMainWindow::closeEvent() is called even if it's overwritten. (Instead of overwriting KMainWindow::closeEvent() the better approach is to overwrite KMainWindow::queryClose() which is what I changed in Kleopatra.)
Mar 11 2025
Which other Qt applications do we want to apply this to? Okular? GpgPass?
For a fresh install with version 4.0.0.250370 (Gpg4win-5.0.0-beta145) all kleo config files are below %APPDATA%\gnupg\kleoaptra:
Backported for VSD 3.3.x / Gpg4win 4.4.x
I believe at least the "automatically" needs to be there.
And you can not close "this" window, really, only all future windows of this kind. If the operation was successfull…
+1 in general; Maybe slightly rephrase to "Close this window after completion"?
tested with Version 4.0.0.250370 (Gpg4win-5.0.0-beta145), works as described.
works, Version 4.0.0.250370 (Gpg4win-5.0.0-beta145)
Confirmed with version 4.0.0.250370 (Gpg4win-5.0.0-beta145), I checked only the default light mode.
Confirmed OK for Version 4.0.0.250370 (Gpg4win-5.0.0-beta145)
Mar 10 2025
Version 4.0.0.250370 (Gpg4win-5.0.0-beta145):
tested with Version 4.0.0.250370 (Gpg4win-5.0.0-beta145) on Windows, works!
with version 4.0.0.250370 (Gpg4win-5.0.0-beta145), Kleopatra from Friday.
We have to talk about the workflows in the different variations. This needs to be simplified further.
I looked with alexk at the suggestion from ikloecker https://dev.gnupg.org/T7091#185587
We would modify it a bit to:
Mar 7 2025
Tested with version 4.0.0.250370 (Gpg4win-5.0.0-beta125)
and Yubikey:
Checked with version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
tested with version 4.0.0.250370 (Gpg4win-5.0.0-beta125): no pop-ups
works, Version 4.0.0.250370 (Gpg4win-5.0.0-beta125)
Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
I think "not certified" is ok if several UIDs with different certification states exist.
Mar 6 2025
Sounds like the animation causes/relies on a deferred destruction. Do we/KF6 delete the popup manually?
Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
Works as described with Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
Making some progress on understanding this:
Mar 5 2025
When opening the notepad in Kleopatra, open it in a new (non modal) window.
This has the advantage that you can to open several notepads.
Kleopatra has currently only two views for the main window: "Certificates" and "Notepad". Using a separate window for the notepad removes necessity for the the "Certificate" button in the icon bar, as well as the corresponding entry in the "View" menu.
That would also make Kleopatra more homogeneous and cleaner.
It is KF6.9.0 in Gpg4win-5.0.0-beta125
The formatted display of the symmetric passphrase is configurable: gpg-agent.conf option pinentry-formatted-passphrase
Ok, the behavior is different depending on if
Oh, then I mistakenly assumed that this behavior is the same in Gpg4win and GnuPG-VSD…
Then this seems to be by design although it does not make sense IMHO to handle this aspect differently between 4win und VSD.
I can find no difference between e.g. gpg4win-4.3.0 and 5.0-beta here:
- The window gets smaller when entering a password in both versions
- there is no whitespace between characters in the old version either
Mar 4 2025
Not reproducible on Linux (with KF 6.11): When clicking the drop down triangle the popup briefly flashes (opens and immediately closes) before the error window is shown. Maybe the bug was fixed in the meantime. Needs to be checked.
In the spirit of making the UI less cluttered, I'd be in favor of removing this line entirely.
a) and b) are both entirely gpg's responsibility. I'm using --status-fd 2 --command-fd 2 to see which messages would be passed to/parsed by gpgme.
$ gpg --version gpg (GnuPG) 2.4.8-beta10
The point here is that I tried to reset with the resetting code, not with the Admin PIN.
As you said we do have an error code for the wrong reset code. Which does not come up.
We do not have an error code for Admin PINs. The Admin PIN is also an OpenPGP card specific termm and other cards use different terms. For example a NKS has no Admin PIN at all but an alternative PIN.
Feb 28 2025
With Gpg4win-Beta60 before the Gpg4win 4.4. release it was "reset code", see https://dev.gnupg.org/T5960#191665, seems there was a change after that
Feb 27 2025
Feb 26 2025
New API gpgme_op_random_bytes is now in master (gpgme 2.0). Use tests/run-genrandom --help for testing. Extra features will come soon.
Remarks:
- This works now on Windows and with the AppImage. This was achieved by customizing the internal application name of Kleopatra: kleopatra-vsd for GnuPG VS-Desktop, kleopatra-gpd for GnuPG Desktop, kleopatra for everything else.
- As a side effect the different flavors of Kleopatra now use different names for the main config file and for the state file, i.e. Gpg4win uses kleopatrarc and kleopatrastaterc, GnuPG VS-Desktop will use kleopatra-vsdrc and kleopatra-vsdstaterc, and GnuPG Desktop will use kleopatra-gpdrc and kleopatra-gpdstaterc.
- The internal application name is also used for config entries retrieved from the registry. That means that for VSD and GPD different registry paths are used in future releases.
- Testing on Windows requires T7040: Make it possible to install GnuPG VSD and GPD in parallel.
Some remarks:
- All Kleopatras use GNUPGHOME/kleopatra for the config files, but they use different names for the main config file and for the state file, i.e. Gpg4win uses kleopatrarc and kleopatrastaterc, GnuPG VS-Desktop will use kleopatra-vsdrc and kleopatra-vsdstaterc, and GnuPG Desktop will use kleopatra-gpdrc and kleopatra-gpdstaterc. That's a side effect of the changes for T7528: Make it possible to run Kleopatra VSD and Kleopatra GPD in parallel where the internal application name is set to kleopatra, kleopatra-vsd or kleopatra-gpd for the different flavors.
- The Kleopatra configuration files are not migrated to the new location. (The group configuration should already have been migrated.)
By the way, this also works for different GNUPGHOME. Tested with a gpgconf.ctl file with content gnupg = gnupg-gpd next to gpgconf.exe.
Kleopatra now writes/reads all config files to/from GNUPGHOME/kleopatra.