On Fri, 6 Jan 2012 23:44, drfar...@acm.org said:
> If there's no security implication (it's hard for me to imagine, but
> I'm not very imaginative) I think ignoring whitespace in the beginning
> and middle of the string makes a lot of sense. I could come up with a
Well, I already did that yeste
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, 6 Jan 2012 14:18, jer...@jeromebaum.com said:
> 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).
Hmmm, you have a point here.
> (In fact I think
On 2012-01-06 13:41, Werner Koch wrote:
> Note that leading and trailing spaces are allowed but the double space
> in the middle of the fingerprint is required:
>
> $ gpg2 -k ' 8061 5870 F5BA D690 3336 86D0 F2AD 85AC 1E42 B367 '
> gpg: error reading key: No public key
Is this necessary fo
On Fri, 6 Jan 2012 11:25, drfar...@acm.org said:
> By quotes, you mean so bash will pass it as one argv? This is
Yes.
> If that works, it'd be great to avoid any extra options. I also agree
> that the colon notation is pretty ugly.
Just commited the change to master:
$ gpg2 -k ' 8061 587
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 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 strings without the help of
delimiters like spaces. Now, if you wa
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 case --recipient can
be
On 2012-01-03 02:52, syka...@astalavista.com wrote:
> Ladies and gentleman, I will be unplugged from my email until the 17th of
> January.
>
> In the mean time here's a video of a bunny opening your mail
> http://www.youtube.com/watch?v=LMyaRmTwdKs
>
> Your mail will not be forwarded and I will
On 2012-01-03 02:43, Daniel Farina wrote:
> Thoughts?
--with-colons
--
PGP: A0E4 B2D4 94E6 20EE 85BA E45B 63E4 2BD8 C58C 753A
PGP: 2C23 EBFF DF1A 840D 2351 F5F5 F25B A03F 2152 36DA
--
nameserver 217.79.186.148
nameserver 178.63.26.172
http://opennicproject.org/
--
No situation is so dire that p
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
11 matches
Mail list logo
