NAI PGP Keyserver with OpenLDAP
Fri Aug 29 16:30:02 2003
> On Wed, Aug 27, 2003 at 04:29:31PM +0200, C.Hackenschmidt wrote:
> > > > Hi again,
> > > >
> > > > Well I just found out that THIS SEEMS TO BE A BUG in the
> > > GnuPG Win32
> > > > Version.
> > > > The Linux version works just fine.
> > > > The key was stored with CR/LF in LDAP. While the Linux
> > > client didn't
> > > > have a problem with that the Win32 version stated no valid
> > > Open PGP data.
> > > > When I store the key only with LF it works for Linux
> and Win32, too.
> > >
> > > Can you give me an example of what you mean? How did you put the
> > > keys into the LDAP server in the first place?
> > >
> > > David
> > Well, in the first place I used ldif-files and ldapadd(OpenLDAP) to
> > store the info in the OpenLDAP-Server.
> > Then I sniffed network traffic with different clients and
> different servers.
> > With this info I found out that the Keys coming from
> > ldap://keyserver.pgp.com don't have CRLF but LF to separate
> the lines
> > and it worked.
> > The keys coming from my OpenLDAP had CRLFs and WinGnuPG
> complained but
> > Linux Version didn't.
> Interesting. The code path that LDAP imports follow is
> actually the same path that file imports follow. Can you try
> creating a CRLF-delimited key file and importing it via
> --import on the Win32 client?
Sure, that's no problem at all. It's like generating one with GnuPG,
exporting, and then importing it again.
Well, that works. I used keys from CAs, too and it worked. Even, like I said
if I copy and paste it from an LDAP-Browser it works.
Only when directly trying to import it via LDAP it doesn't and only with
WinGnuPG. This seems really bizarre, doesn't it.
Could it be a compiling problem?