Also works in VSD-beta-478
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 7 2025
works as expected with beta 478
works with VS-Desktop-3.2.94.474-Beta, too
removing the gpgcom tag as its only relevant for vsd and is already backported
Backported for VSD 3.3
As discussed offline we continue in this ticket.
Please resize to content when the search results are shown, for the first time only.
Additionally name and emails should have the default column with of the certificate list.
Should I close this ticket again and make a new one for the width of the result?
Seems I did not test this sufficiently. This is how the very first Search on a new installation looked with VS-Desktop-3.2.94.474-Beta:
Jan 6 2025
Backported for VSD 3.3
This is ok in VS-Desktop-3.2.94.474-Beta but in the EN version the SecOPs are missing because of a missing file during build.
-> Check again with the next build
Jan 3 2025
Jan 2 2025
@ikloecker: Do you still have the private key for tests/json/key-with-revokers.asc somewhere? We need to remove the expiration date due to T7471.
Dec 20 2024
Looks like gpg 2.2 doesn't emit a canceled status log message, but gpg 2.4 does if the problem only occurs with VSD but not with Gpg4win.
Works, tested with VS-Desktop-3.2.94.474-Beta
The layout is totally different now in VS-Desktop-3.2.94.474-Beta but the "generate new key" action is now hidden for the slots (while still there in Gpg4win 4.4).
Works. Tested with VS-Desktop-3.2.94.474-Beta and Gpg4win 4.4
Dec 19 2024
Works. Tested with VS-Desktop-3.2.94.474-Beta and Gpg4win 4.4 by moving only the signature key to a smartcard and then changing the password of the certificate via the context menu.
Dec 18 2024
Backported for VSD 3.3.
Dec 17 2024
Dec 16 2024
I looked at the wiki and the content seems okay and what this issue requests has been done years ago. So resolved.
No longer valid.
Backported for VSD 3.3
closing, as there is a follow up ticket
Let's backport this for VSD 3.3 even if https://dev.gnupg.org/T7227#195685 is just a cosmetic issue. The first impression counts.
Apart from checking the gpgme logs to see if validation is enabled for the key listing this can be tested indirectly by verifying that the Status column isn't too narrow after generating a new certificate in an empty keyring in a VSD version (see https://dev.gnupg.org/T7227#195685).
In T7227#195685, @ebo wrote:The status column is not wide enough.
There's the VERSION file that is used for customizing the About data for VSD and GnuPG Desktop. It's an ini format file that's read with QSettings.
Doing the changes to the text is easy enough, but I'm not sure whether we have a nice way of doing something only in a VSD version.
The changes had to be reverted, a working solution is planned for later