Hi all, I'm setting up a local LDAP server with a pass-through authentication to another LDAP. I'm not clear about the encryption.
Say the case is like this. CompB is set to have LDAP authentication. A ---> SSH ---> CompB ---> Local LDAP:389 ---> SASLAUTHD --> Global LDAP: 636
1. Password on the SSH session would be encrypted, isn't it? 2. How about when it goes to the local LDAP:389, would it be encrypted?
Thank you. Fajar.
On Wednesday 15 February 2012 08:46:02 Fajar Priyanto wrote:
Say the case is like this. CompB is set to have LDAP authentication. A ---> SSH ---> CompB ---> Local LDAP:389 ---> SASLAUTHD --> Global LDAP: 636
- Password on the SSH session would be encrypted, isn't it?
- How about when it goes to the local LDAP:389, would it be encrypted?
AFAIK not, it won't be encrypted. However, the only way to read that information would be to already have access to your computer (so you'd be screwed anyway)
Regards
On Feb 14, 2012, at 5:46 PM, Fajar Priyanto wrote:
Hi all, I'm setting up a local LDAP server with a pass-through authentication to another LDAP. I'm not clear about the encryption.
Say the case is like this. CompB is set to have LDAP authentication. A ---> SSH ---> CompB ---> Local LDAP:389 ---> SASLAUTHD --> Global LDAP: 636
- Password on the SSH session would be encrypted, isn't it?
---- ldaps (port 636) would indeed be encrypted but it is deprecated and not typically started by default configurations these days. ----
- How about when it goes to the local LDAP:389, would it be encrypted?
---- depends upon whether TLS is indicated and/or required.
If you require it via an ACL on the LDAP server, then it succeeds only if the connection is made via TLS.
If you require it at the client (TLS_ReqCert demand or hard), then it succeeds only if the connection is made via TLS.
Craig
On Thu, Feb 16, 2012 at 7:34 AM, Craig White craig.white@ttiltd.com wrote:
Say the case is like this. CompB is set to have LDAP authentication. A ---> SSH ---> CompB ---> Local LDAP:389 ---> SASLAUTHD --> Global LDAP: 636
- Password on the SSH session would be encrypted, isn't it?
ldaps (port 636) would indeed be encrypted but it is deprecated and not typically started by default configurations these days.
- How about when it goes to the local LDAP:389, would it be encrypted?
depends upon whether TLS is indicated and/or required.
If you require it via an ACL on the LDAP server, then it succeeds only if the connection is made via TLS.
If you require it at the client (TLS_ReqCert demand or hard), then it succeeds only if the connection is made via TLS.
Thanks for the thoughts so far. When I setup TLS on the local LDAP, somehow the saslauthd fails to authenticate the password with Global LDAP. The admin said that the Global LDAP doesn't support TLS, only SSL.
Basic question... What's the different between TLS and SSL in LDAP? I googled no clue yet.
On 02/15/2012 08:20 PM, Fajar Priyanto wrote:
Basic question... What's the different between TLS and SSL in LDAP? I googled no clue yet.
A plain-old LDAPS (LDAP over SSL) connection starts off from the very beginning as an SSL connection on port 636. When using LDAP and TLS, the initial (unencrypted) connection is made to port 389 and the SSL connection is negotiated on-the-fly. Logically, the unencrypted connection is made initially, then the client and server start up an SSL handshake if both ends support it.
The LDAP-over-SSL (LDAPS) method as been deprecated and the preferred method is LDAP and TLS. The TLS method is no less secure as the only thing that goes over the wire unencrypted is the SSL handshake.
Just my $.02
-
Craig White -
Fajar Priyanto -
Jay Leafey -
Marc Deop