Ok with me. setting this to resolved, then.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 8 2024
keep in mind https://dev.gnupg.org/T7217#193778 when tackling this task
I like it better than the very long tool tip.
Testing the removal of the appearance flag from this filter leads to this situation:
Hm, probably I would be for the html-tags, then. Is there an example where one could see how narrow tool tips really get with that option?
We shouldn't have to add explicit line breaks. Explicit line breaks will lead to bad formatting (German: Flattersatz) for people who use huge font sizes (a11y!) and Qt will wrap long tool tips so that they won't become wider than the screen. Alternatively, we wrap the tool tips (in the code that sets the tool tips) into <html> tags. Then (for whatever reason) Qt will make the tool tips much narrower. (Some people think too narrow, but we have to die one death.)
setting this to open for the small fix in the tooltip.
I suggest as new text:
"Disabled certificates are not offered when selecting a certificate to sign with or to encrypt for.\nThey are not shown in the certificate list with most filters."
And I think there should be an additional newline somewhere, as I was shown a much too long tool tip. The German text is not that much longer…
Removing the appearance filter won't fix own disabled certificates not being bold; the problem here is that the "My certificates" filter doesn't trigger at all anymore for disabled certificates
Agree with removing the appearance filter
Yeah. so lets ditch that appearance filter. But that's for ticket T7217. So I'm setting this ticket to done for 4win.
Nov 7 2024
You mean that a disabled certificate with secret key isn't listed with bold font? That's probably because we have an appearance filter for disabled certificates which takes precedence.
I agree that it doesn't make sense anymore because we never show disabled and not-disabled certificates next to each other.
Fixed for all branches.
Gpg4win-Beta-70:
Looks ok.
Gpg4win-Beta-70:
There is an appearance filter for disabled certificates now.
Though I wonder if it is really necessary / useful, as we now have regular filters, too. I would have thought we only need the regular filters. I think the appearance filter was to be a stopgap as we did not want to touch the filters at the time when this ticket was created.
What do you say?
Gpg4win-Beta-70:
All 4 items in the task description are realized as described.
gpg4win-Beta-70: works.
I disabled a certificate, it was not shown anymore in the "all" view. Change to the "Disabled" filter and enabled it again -> it shows again with the "All" filter.
Disabling a private certificate does not allow it for signing and not for encrypting to it. It is also not offered for these any more.
But verifying files which were signed by it works.
I managed to get the same "loading certificate" message several times in a row on this test instance by stopping and starting Kleopatra in a row twice. After removing the Signature Card 2.0 this did not happen again in 5-6 tries, although I collected 2 lingering listing processes again (not both started on the same startup). Even import of a X.509 certificate worked.
I have updated the translations of the filters defined in the libkleopatrarc*.desktop files.
Next I managed to have one gpg and one gpgsm process each left over from the last execution of Kleopatra.
After starting Kleopatra new anyway, again "loading certificate cache" and an additional pair of gpg and gpgsm listing processes start.
Had a occurrence of the never ending "loading certificate cache" issue again.
There was a leftover gpgsm process from the previous tests (although Kleopatra warned when I closed it, that processes still running in the background were there and would be aborted).
gpg4win-Beta-70:
The tooltips are all there now.
But some of the tooltip translations are missing and need to be merged/copied still.
So I'm moving this to backlog, so we do not forget this
works, gpg4win-Beta-70.
In T7379#193696, @ikloecker wrote:I assume by "do such things in the background" you mean that GnuPG should do this automatically in the background.
SCD SERIALNO serialno can move the first card in the list in scdaemon.
I assume by "do such things in the background" you mean that GnuPG should do this automatically in the background.
@ikloecker Using scdaemon with multiple cards, it is a connection which holds the card.
Support for NKS (Telesec NetKey card and Signature card v2, both based on TCOS) is very old and predates the support for multiple applications. They are also not as well separated as with Yubikey applications. Thus the auto switching between the NKS app and the SigG app.