storing gpg keys on a database

David Shaw dshaw at jabberwocky.com
Tue Jan 20 14:54:55 CET 2009


On Tue, Jan 20, 2009 at 10:10:43AM +0100, Ramon Loureiro wrote:
> David Shaw wrote:
> > On Mon, Jan 19, 2009 at 11:43:21AM +0100, Ramon Loureiro wrote:
> >   
> >> Werner Koch wrote:
> >>     
> >>> On Mon, 19 Jan 2009 11:23, ramon.loureiro at upf.edu said:
> >>>
> >>>   
> >>>       
> >>>> Could you give me some references (libraries, structures...) on how to
> >>>> store GPG keys on a database?
> >>>>     
> >>>>         
> >>> Export them _without_ the option --armor and store them as a binary blob.  
> >>>
> >>>
> >>>   
> >>>       
> >> Hi,
> >>
> >> Thanks, but I'd like to build an application to quick search for keys
> >> and the input should be an email...
> >> If I have to export on the fly every key, it will be very slow.... isn't?
> >>     
> >
> > Almost everything you need is done for you: set up a keyserver.
> >   
> And does a keyserver use a database? or is it based on a filesystem and
> on the fly operations?
> (I know how to handle online-databases (mySQL, Postgres...) with perl,
> pyton or PHP but I don't know anything about LDAP...)

You can think of an LDAP keyserver as a database.  It stores data, and
there is a query language to retrieve data in various ways.

> My idea is having these structures to easy see who has signed someone's key

You can do this in LDAP with something like
(&(pgpcertid=long-key-id)(pgpsignerid=other-long-key-id))

> So I "only" need to store the fingerprint, the email and the signatures...

Hard to say - it's not clear what you're trying to do and why, so
we're all sort of feeling around in the dark.  Why don't you say what
you're trying to do, and we can help?

David



More information about the Gnupg-users mailing list