SUMMARY: Solaris 8 ldapclient with TLS

From: Bousquet Francois (Francois.Bousquet_at_cgi.com)
Date: 03/24/05

  • Next message: Bousquet Francois: "Old server replacement suggestion" 
    To: "Mailing List - SunManagers (E-mail)" <sunmanagers@sunmanagers.org>
Date: Thu, 24 Mar 2005 17:14:13 -0500

    Seems to resume everything...

    -----Original Message-----
    From: Todd Wilkinson [mailto:todd.wilkinson@gmail.com]
    Sent: March 23, 2005 7:43 PM
    To: Bousquet Francois
    Subject: Re: Solaris 8 ldapclient with TLS

    Solaris 8 default ldapsearch doesn't have it but the ldapclient does
    if you are patched up with 108993-38+ ( actually the recent -43 is
    better ). Solaris 9 default ldapsearch doesn't have tls but the
    iplanet ldapseach on solaris 9 does (
    /usr/iplanet/ds5/shared/bin/ldapsearch ) and the default solaris 10
    ldapsearch does have tls support as well as native tls in the
    ldapclient.

    bottom line ldapsearch and ldapclient are two seperate things and
    solaris 8,9 and 10 does in fact support tls. :)

    On Wed, 23 Mar 2005 11:17:40 -0500, Bousquet Francois
    <Francois.Bousquet@cgi.com> wrote:
    > I am trying to setup ldapclient with TLS on Solaris 8
    >
    > My topic on Sun's forum :
    >
    http://supportforum.sun.com/sunos/index.php?t=msg&th=2562&start=0&rid=8234&S
    > Q=e4e017e8fd082398859368b288f272eb
    >
    > Anyone have an idea or clue how to test an LDAP TLS connexion with Solaris
    > 8. I've try ldapsearch with it don't seems to have any tls capability ...
    >
    > thanks
    >
    > Francois
    > _______________________________________________
    > sunmanagers mailing list
    > sunmanagers@sunmanagers.org
    > http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Bousquet Francois: "Old server replacement suggestion"

    Relevant Pages

    • Re: 64-bit instructions in 32-bit code
      ... Piotr Wyderski wrote: ... > Thank you for your help, Casper, but could you please answer one more ... > Which thread-local data access method is the fastest on Solaris? ... > TLS key-based indexing, key range checking etc. is required. ...
      (comp.unix.solaris)
    • Re: Solaris 8 nss_ldap frustration
      ... Solaris ... except ldapclient doesn't really work. ... The main difference between pam_unix_auth and pam_ldap is that with pam_unix_auth the local client makes the decision of whether or not the user has succeeded with authentication, while with pam_ldap the ldap server decides if authentication is successful. ...
      (comp.unix.solaris)
    • changing ldapclient
      ... which uses a SunDirectory 5.1 SP2 for Naming Service. ... Now i'm try to switch the Directory to a new 5.2 version which Solaris9 Server ... I've noticed that Solaris 8 requires the objectclass ...
      (SunManagers)
    • Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
      ... I was doing some testing, using ldapsearch from a Solaris machine, to ... fully-qualified domain name (FQDN) for the hostname parameter. ... Any ldap search is FQDN based to 'find' the ldap server. ... The machine from which I was running the ldapsearch was a Solaris X86 box, so it wasn't a member of any Windows domain. ...
      (microsoft.public.win2000.active_directory)
    • Re: Possibly slightly O.T.: Why FQDN required to do simple bind with "ldapsearch"?
      ... I was doing some testing, using ldapsearch from a Solaris machine, to access Active Directory. ... I was trying to use a simple bind, and initially could not get a successful access, until I started using a fully-qualified domain name (FQDN) for the hostname parameter. ... I'm not sure if this is more of an AD question, or an ldapsearch question, but I was wondering if anyone might know why I had to use the FQDN for the ldapsearch hostname parameter in order for the simple bind to succeed? ...
      (microsoft.public.win2000.active_directory)