[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: SSL/GSSAPI for OpenLDAP

To: David Boreham <dboreham@netscape.com>
Subject: Re: SSL/GSSAPI for OpenLDAP
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Mon, 14 Jun 1999 15:36:40 -0700
Cc: Julio Sánchez Fernández <j_sanchez@stl.es>, shltch@osfmail.isc.rit.edu, openldap-devel@OpenLDAP.org, bart@OpenLDAP.org
Organization: OpenLDAP <http://www.openldap.org/>
References: <Pine.OSF.4.05.9906111551350.9893-100000@grace> <3.0.5.32.19990614144804.00988eb0@localhost> <3.0.5.32.19990614151759.0091bbd0@localhost> <3765848E.4FBF21BC@netscape.com>

David Boreham wrote:

> You'll probably find that you need some sort
> of unread operation too. I did for the server.
> Big PITA it is too.

I'm thinking that this could be avoided by having a dataAvailable
hook...  but, yes, something is needed to manage issues concerning
low-level I/O availability and ber-level data availability.
That is, a socket can be selectable but no data is yet available
due data decryption requirements.

References:
- SSL/GSSAPI for OpenLDAP
  - From: shltch@osfmail.isc.rit.edu
- Re: SSL/GSSAPI for OpenLDAP
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: SSL/GSSAPI for OpenLDAP
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: SSL/GSSAPI for OpenLDAP
  - From: dboreham@netscape.com (David Boreham)

Prev by Date: Re: SSL/GSSAPI for OpenLDAP
Next by Date: RE: SSL/GSSAPI for OpenLDAP
Index(es):
- Chronological
- Thread