- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 26 2024
Oct 25 2024
This bug exists since Kleopatra offers "Trust root certificate" (i.e. since 2010). allow-mark-trusted seems to be default since Gpg4win 2.1.0. If admins really want to prevent users from messing with the trustlist then they anyway have to use the no-user-trustlist option.
I can still reproduce case 2 with gnupg 2.4. I have to check how my local setup differs from gpg4win-Beta-64.
If we fix this bug for 2.2 we need to have a configure way to revert to the old behaviour. That needs to be a kleopatra config. Or we just don't fix this bug for current vsd but only for gpg4win and the next generation vsd.
Solved for gnupg 2.2, 2.4 and 2.6. GPGME support still missing.
If you use a tabbed layout you will always have the problem that some tabs have lots of whitespace and other tabs have little whitespace or even a scrollbar.
I just saw that gpg-agent has a MARKTRUSTED command which takes care of asking the question and of modifying the trustlist.txt. I guess it makes sense that Kleopatra uses this command for the "Trust root certificate" action.
In T7349#192860, @werner wrote:Kleopatra should also not offer to add a root CA if gpg-agent's mark-trusted feature has been disabled.
Saw it in a screenshot somewhere, can't find it now. I do not have a version with that commit.
Oct 24 2024
In T7329#192861, @ebo wrote:Regarding the removal of the stretch: Now there seems to be no space at all before the description. Could we have a one-line space before it?
I have confirmed that rA69069bc63e6b fixes the build on macOS.
As this ticket is for vsd33, the nice design tweak has to go into another ticket, it will not be backported to kf5.
iirc, Kleopatra modifies the trustlist.txt on its own. The import case is handled by gpgsm which pops up boths dialogs.
Kleopatra should also not offer to add a root CA if gpg-agent's mark-trusted feature has been disabled.
When checking this out with gpg4win-Beta-64 I can reproduce case 1 (and of course 3) but not case 2:
Regarding triage: This is not widely encountered and a workaround exists
Passing ticket to werner to consider backports.
I created a branch: https://dev.gnupg.org/source/libgcrypt/history/gniibe%252Ft7340/
Oct 23 2024
A bunch of related merge requests:
This is now merged into master
Also done for gpgsm in gnupg26 (master)
Thanks. Fixed in: rEd14c69a7f256: Avoid use of 'nullptr' for an identifier.