IIRC, support for the keybox fomat was added on Debian's request with 2.1.7 in 2015 to gpgv. In fact gpgv was written on Debian's request (1.0.4 from fall 2000).
bernhard renamed
T8122: Instruction to install https://repos.gnupg.org/deb/gnupg/trixie/ fail in 1st variant because of keybox use (Error: Failed to parse keyring "/usr/share/keyrings/gnupg-keyring.gpg") from
Instruction to install https://repos.gnupg.org/deb/gnupg/trixie/ fail for sqv Error: Failed to parse keyring "/usr/share/keyrings/gnupg-keyring.gpg" to
Instruction to install https://repos.gnupg.org/deb/gnupg/trixie/ fail in 1st variant because of keybox use (Error: Failed to parse keyring "/usr/share/keyrings/gnupg-keyring.gpg").
IIRC, support for the keybox fomat was added on Debian's request with 2.1.7 in 2015 to gpgv. In fact gpgv was written on Debian's request (1.0.4 from fall 2000).
I guess you need to report this to Debian
I'm okay with omitting the list of suggestions for shared secret keys. The person distributing the key should have told the recipients how to import and certify them properly.
Also backported for VSD 3.4.
Now also available in Gpg4win 5.
Save CSRs that were generated in PEM format with suffix .pem
Add setting for format of CSRs
Add setting for format of CSRs
Save CSRs that were generated in PEM format with suffix .pem
doc: Update Known Problems section in README.
gpg:keygen: Add ECC information for composit keys.
Ready for testing in VSD 3.3
kleopatra: Add patches to optionally save CSRs as PEM
Thomas Friedrichsmeier <thomas.friedrichsmeier@kdemail.net> committed
rKLEOPATRAddabe7bf6167: Remove obsolete - and broken - wayland clipboard workaround (authored by Thomas Friedrichsmeier <thomas.friedrichsmeier@kdemail.net>).
Remove obsolete - and broken - wayland clipboard workaround
Thomas Friedrichsmeier <thomas.friedrichsmeier@kdemail.net> committed
rKLEOPATRAab5132945e2c: Remove obsolete - and broken - wayland clipboard workaround (authored by Thomas Friedrichsmeier <thomas.friedrichsmeier@kdemail.net>).
Remove obsolete - and broken - wayland clipboard workaround
I guess you need to report this to Debian as their new sqv tools seems to be broken.
Merge branch 'master' of ssh://git.gnupg.org/git/gpgol
Make keyboard navigation in tables work again
Make keyboard navigation in tables work again
How about changing the text after sentence two simply to:
I guess you need to report this to Debian as their new sqv tools seems to be broken.
A workaround I've found is to give the public key directly in /etc/apt/sources.list.d/gnupg.sources.
Update gpgme from 1.24 to 2.0
Simplify auto-attach keys action
Detect and offer to import OpenPGP keys in attachments / Autocypt headers
Initial draft for auto-attaching PGP keys
Attach recipient keys, only if more than one (non-BCC) recipient
Fix race conditions during startup on Windows
In single-user mode, pair clients, automatically
Cleanup, and regenerate web files
Limit client connections to same origin IP
In single user-mode, ensure native client never connects to foreign proxy
Trying to do the verification outside of apt-get:
Change extension page layout to use buttons, again
Ensure proxy server is available during first time setup
Remove most of troubleshooting, for less intimidation
Fully implement connection status display
Split and redesign FirstTimeDialog
Keep filename of root-ca fixed per user (to allow re-installation)
Rename manifest.po to avoid potential name clash
Localize manifest strings while generating the manifest
Add git commit info to about dialog
Add git commit info to about dialog
Update gpgrt, libassuan, libksba, gpgol, gpgex to current versions.
Update of libpng to 1.6.53
Random mode ZBase32 not currently usable on Windows
Random mode ZBase32 not currently usable on Windows
• werner renamed
T7174: Release libksba 1.6.8 from
Release libksba 1.7.0 to
Release libksba 1.6.8.
• werner edited Description on
PQC.
Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?
Fix race conditions during startup on Windows
Rename manifest.po to avoid potential name clash
Localize manifest strings while generating the manifest
Cleanup, and regenerate web files
What about always using PEM for all generated CSRs? As far as I can see, gpgsm command line always uses PEM when generating CSRs.
Detect and offer to import OpenPGP keys in attachments / Autocypt headers
Simplify auto-attach keys action
Attach recipient keys, only if more than one (non-BCC) recipient
Initial draft for auto-attaching PGP keys
In single-user mode, pair clients, automatically
Cleanup, and regenerate web files
In single user-mode, ensure native client never connects to foreign proxy
Also save drafts in new common path
Explicitly share certain paths between client and server
Limit client connections to same origin IP
Ensure proxy server is available during first time setup
Fully implement connection status display
Change extension page layout to use buttons, again
Remove most of troubleshooting, for less intimidation