[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: developer.php reporting wrong key for weasel



On Mon, 02 Aug 2004, Igor Genibel wrote:

> Le samedi 31 Juillet 2004 00:07, Peter Palfrader a écrit :
> > Hi everyone,
> 
> Hi Peter,
> 
> > |   General information: (collapse) GPG key id: [2]D097A261
> >
> >                                                    ^^^^^^^^
> >
> > |   [3]Non-fixed bugs, most recent first
> >
> > This is not my keyid, something apparently went wrong when generating
> > one of the files.
> 
> Fixed now

Thanks.

> > PPS: Looking at ddpo.y I see you parse keyserver's output.  SKS
> > supports "&options=mr" which gives you an easy to parse output, you
> > might want to use that.
> 
> It would be great if I could find a way to deal with revoked/expired keys
> For example with my previous gpg key (revoked) 0x9D735B4F
> http://keyserver.fabbione.net:11371/pks/lookup?search=0x9D735B4F&options=mr
> I can't find such information

I've fixed keyserver.noreply.org to show that information.  Patch sent
upstream.

> >  It is similar to the output used by gpg when you pass --with-colons,
> > which you also might want to use, for results/dev_keys
> 
> Hum, only the regexp would change. 

The human readable interface can change at any time, while the machine
readable output is supposed to stay the same.

-- 
Peter



Reply to: