Opened 13 years ago
Closed 13 years ago
#34120 closed defect (duplicate)
OpenSSL 1.0.1_2 - TLS can't connect
| Reported by: | sawright@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | Cc: | ||
| Port: | openssl |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Trying a basic ldapsearch:
ldapsearch -d 1 -x -L -v -H ldaps://ldapauth.lbl.gov:636
Fails:
TLS: can't connect: . ldap_err2string ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
Change History (3)
comment:1 Changed 13 years ago by pixilla (Bradley Giesbrecht)
comment:2 Changed 13 years ago by sawright@…
Unfortunately that won't work for me. My main use for this is a web login that's running php to process the ldap commands (via the openSSL library). It's been working smoothly until I did this latest update.
Thank you for pointing out the other thread. I'm sorry I didn't find that one and post my issue to it.
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Keywords: | OpenSSL removed |
| Port: | openssl added; OpenSSL removed |
| Resolution: | → duplicate |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Other openssl dependent packages are having trouble with openssl 1.0.x. #33715
Does your ldap implementation expose a way to select the openssl ciphers?
Using "curl --ciphers" is working for me with openssl 1.0.x.