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
1. Password on the SSH session would be encrypted, isn't it?
2. How about when it goes to
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
On Thu, Feb 16, 2012 at 7:34 AM, Craig White craig.wh...@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
1. Password on the SSH session would be encrypted, isn't it?
ldaps
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
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
5 matches
Mail list logo