On Tue, Jan 31, 2012 at 11:35 AM, Jerry wrote:
> On Tue, 31 Jan 2012 12:26:07 -0500
> Christopher J. Walters articulated:
>
>> It was my understanding that this bug had been fixed in Thunderbird,
>> but I may be mistaken. I know that in a GNU/Linux user mailing list
>> I have long been signed up
On Fri, Jan 6, 2012 at 5:18 AM, Jerome Baum wrote:
> Is this necessary for a technical reason? I'm just thinking about the
> scenario where transmits his human-readable fingerprint in a medium that
> collapses repeated spaces (think e.g. HTML).
If there's no security implication (it's hard for me
On Fri, Jan 6, 2012 at 2:17 AM, Werner Koch wrote:
> On Fri, 6 Jan 2012 00:12, drfar...@acm.org said:
>
>> Should that become the default? What's the use of nibbles that cannot
>
> No, --with-colons is not for humans. OTOH, humans are not able to
> properly read and compare 40 digits hex string
On Mon, Jan 2, 2012 at 5:49 PM, Jerome Baum wrote:
> On 2012-01-03 02:43, Daniel Farina wrote:
>> Thoughts?
>
> --with-colons
Should that become the default? What's the use of nibbles that cannot
be parsed by --recipient?
I also prefer to read the whitespace, but in that
Hello list,
I was recently trying to encrypt a payload using fingerprints in my
keyring to most unambiguously identify a key, when I encountered the
following confusion. After giving up trying to find resolution via
search engine I played with it a bit more I got it to work, but the
head-scratchi
Hello list,
I've been integrating GPG into a backup utility, and while OpenPGP
works as expected, I'm having some trouble with trying to also enable
self-signed x509 certs via gpgsm as a mechanism for encryption.
Unfortunately all I get back from gpgsm is "No Value". The output of
a gpgsm invocat
