Today
ok, lets do this. I'll update the description
I'm fine with just dropping it.
One doesn't even need a global config file to reproduce the duplication.
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).
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.
Yesterday
Ready for testing in VSD 3.3
I guess you need to report this to Debian as their new sqv tools seems to be broken.
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.
Trying to do the verification outside of apt-get:
Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?
What about always using PEM for all generated CSRs? As far as I can see, gpgsm command line always uses PEM when generating CSRs.
Panel Used By
| Dashboard | aa7356's Dashboard |