Re: [Sks-devel] acceptable search input format

[John Clizbe]

David Shaw wrote:
> On Jun 4, 2014, at 4:52 AM, kwadronaut <address@hidden> wrote:
> 
>> Hi,
>> 
>> I noticed that the search for keys in the web fronted is picky in its
>> input. Some that should work (in my opinion) don't. I double checked
>> with 'How to specify a uid' in gnupgs documentation [1]. Is there any
>> rationale to limit the search like it's done currently, or would it be
>> an improvement to also look for fingerprints, long and short keyids when
>> the 0x isn't specified at the front? An improvement for end users that
>> is, given that I don't run any sks servers myself, I'm not paying
>> attention to possible drawbacks for server operators.
>> 
>> NOK
>> 1202821CBE2CD9C1
>> 1202821CBE2CD9C1
>> 0D24B36AA9A2A651787876451202821CBE2CD9C1
>> 
>> OK
>> 0x1202821CBE2CD9C1
>> 0xBE2CD9C1
>> 0x0D24B36AA9A2A651787876451202821CBE2CD9C1
> 
> The rule is "All key ID searches start with 0x.  Non-key-ID searches don't."
> 

In the code, key ID searches run against the keyid table. Non-key ID searches
target the word table. I believe this behavior was inherited from the pksd
code base.

-John

-- 
John P. Clizbe                      Inet: John (a) Gingerbear DAWT net
SKS/Enigmail/PGP-EKP                  or: John ( @ ) Enigmail DAWT net
FSF Assoc #995 / FSFE Fellow #1797  hkp://keyserver.gingerbear.net  or
     mailto:address@hidden

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

signature.asc
Description: OpenPGP digital signature