Today
Initial version in work/tfry/trustlevel.
Backported for VSD 3.4
Fixed. Kleopatra now looks for programs given as plain name (i.e. without any path) first in the GnuPG installation path (as reported by gpgme) and then next to the kleopatra executable. If the program is found at neither location it is run as-is.
For "expired signature with certified key" I believe green with check mark is a too positive. Should be a warning, too.
Due to Apache doc this is a permission problem:
But it's still not working!
The text is exactly as discussed and I'm OK with the layout, too.
The AppImage now displays the same version as the Windows builds, i.e. in particular Gpg4win-VERSION for the "default" build.
I was told to only fix this in the German translation, as otherwise all other translations would have to be updated.
I'll push the translations shortly.
I found two issues in libgpg-error for spawning functions.
POSIX documentation never says that PSHARED=0 prevents sharing among processes. In my opinion, it still conforms to POSIX even when a PSHARED=0 semaphore can be shared between parent and child processes.
Yesterday
With the recent changes to the build system the current version numbers for the Beta versions of the MSI packages are 4.0.90.<somenumber> for VSD, 5.0.90.xxx for GPD and Gpg4win. Thus we override the standard micro version with 90 to indicate beta versions. Obviously this will require to de-install a MSI beta version before installing the regular version. But we are somewhat constraint by the Windows versioning scheme.
Will go into 1.12.1
Thanks. Will go int the next version.
Got reported again with the 5.0.0 release, see
Is this wording / layout okay?
Is the displayed version 4.0.0.260370 right for the appimage? shouldn't this also display the gpg4win version?
Looks good to me on gpg4win-5.0.1-beta24 @ archllinux:
The display in Okular is independent from Kleopatra, so dropping it in Kleopatra should be fine.
If a QES certificate is available, Okular should highlight and add a filter for them (which is currently not working, see T6632: Okular: Highlight / preselect "nonRepudiation" certificates for qualified signatures)
I currently have a slight preference to drop bold and go with normal font. Werner would be ok with that, too.
a) Here's a log anyway (ignore it, if decryption does always work):
@svuorela said, QES certs shouldn't be required to be on a smartcard.
Using an icon for QES certificates isn't that easy because we use an icon for smartcard certificates and any list item can have at most one icon. Moreover, QES certificates are very like stored on a smartcard (isn't that even a requirement?), i.e. an icon clash is basically guaranteed.
Additionally, the de-vs-compliance filters are no longer show in non-compliant installations like Gpg4win.
In T6632: Okular: Highlight / preselect "nonRepudiation" certificates for qualified signatures I had the impression, that some hint is useful for signing operations. Probably not so much in general.
Done and backported for VSD 3.4
checked with vsd 3.3.5: no change
I've tried the new patch in my environment, and it fixes the gnupg HEAD self tests as well. Thank you!
Highlighting QES is mostly useful for Okular, I guess.
Maybe use a symbol with a pen? That should be self-explanatory.
We'll go with solution no 2 (which is in effect the same as no 1 anyway)
I misunderstood this, the mail can be forwarded with attachment if you first deselect the mail and then select it again. So the workaround is OK.
We decided to still use the term "Valid" (with description/tooltip "Certificates that are neither expired nor revoked (except disabled ones)"). This matches the use of the term "invalid" for expired and revoked certificates as in "Certificates that are invalid because they have expired (except disabled ones)".
Panel Used By
| Dashboard | Mitzie209's Dashboard |