Hi,
This must be something simple I'm missing but on a debian stretch 64
machine i cannot get gpg 2.1.10 compiled with bzip2 support which
prevents me from reading bzip2 compressed files - they can decrypt but:
gpg: uncompressing failed: Unknown compression algorithm
./configure
Can anybody confirm on debian stretch 64 a successful build with
libgcrypt beta ?
checking for LIBGCRYPT - version >= 1.6.0... yes (1.7.0-beta300)
checking LIBGCRYPT API version... okay
i cannot create curve25519 encryption sub keys
gpg: agent_genkey failed: Invalid flag
gpg: Key generation
Hi!
> Do I have to sign it? Is there no way to configure gpg locally to
> say "the info in this key (fingerprint) is accurate", without having
> to sign?
You have to sign it; that's how it works :).
> Is the semantics of signing with lsign or sign "the info in this key
> is accurate"?
Yes.
On 01/10/2016 11:01 PM, Full Name wrote:
Do I have to sign it? Is there no way to configure gpg locally to
say "the info in this key (fingerprint) is accurate", without having
to sign?
If you are using the default trust model ("pgp"), no. In this model, the
validity of a key is only
On 01/10/2016 02:01 PM, Full Name wrote:
Do I have to sign it? Is there no way to configure gpg locally to
say "the info in this key (fingerprint) is accurate", without having
to sign?
Is the semantics of signing with lsign or sign "the info in this key
is accurate"?
You've already received
>
>
>> You've already received good answers on your questions, so some questions
> for you. :) What is your concern about signing the key? And are you aware
> that local signatures will not be communicated beyond your keyring?
I actually ran into this issue the other day. For me it's
Am 11.01.2016 um 17:35 schrieb Lachlan Gunn:
>>
>>
>>> You've already received good answers on your questions, so some questions
>> for you. :) What is your concern about signing the key? And are you aware
>> that local signatures will not be communicated beyond your keyring?
>
>
> I actually
