Paul Henry
2005-Jul-24 21:39 UTC
[Samba] logon drive, ldap ssl = start_tls, ssh and client/server encryption (and logon.bat permission tip)
Dear list, More questions on my PDC travels ;-) 1. Is it ok, with roaming profiles on, to leave "logon drive = " empty, as this drive seems to be confusing users? 2. All my ldap stuff is using tls, and I just want to confirm that "ldap ssl = start_tls" is looking in /etc/ldap.conf for certificate locations etc.? 3. Is all traffic between Windows clients and the Samba server encrypted, or can this be done/how? 4. Nowhere in Samba How-To or Samba-Guide did it say that the logon.bat (logon script, whatever you wish to name it) should be permission 744, i.e. chmod 744 could we add this? 5. Why do you need to ldap enable sshd via pam? This lets any domain user log into the server. I think this is a bad idea, unless you are providing shell access for some reason? Thanks for your time, Paul.
Paul Henry
2005-Jul-26 09:31 UTC
[Samba] Fwd: logon drive, ldap ssl = start_tls, ssh and client/server encryption (and logon.bat permission tip)
Anyone shed any light for me? Thanks, Paul. ---------- Forwarded message ---------- From: Paul Henry <samba.user@gmail.com> Date: 24-Jul-2005 22:38 Subject: logon drive, ldap ssl = start_tls, ssh and client/server encryption (and logon.bat permission tip) To: samba@lists.samba.org Dear list, More questions on my PDC travels ;-) 1. Is it ok, with roaming profiles on, to leave "logon drive = " empty, as this drive seems to be confusing users? 2. All my ldap stuff is using tls, and I just want to confirm that "ldap ssl = start_tls" is looking in /etc/ldap.conf for certificate locations etc.? 3. Is all traffic between Windows clients and the Samba server encrypted, or can this be done/how? 4. Nowhere in Samba How-To or Samba-Guide did it say that the logon.bat (logon script, whatever you wish to name it) should be permission 744, i.e. chmod 744 could we add this? 5. Why do you need to ldap enable sshd via pam? This lets any domain user log into the server. I think this is a bad idea, unless you are providing shell access for some reason? Thanks for your time, Paul.
Seemingly Similar Threads
- Samba 2.2.5 and LDAP start_tls
- ldap start_tls to microsoft active directory
- Patch for 2.2.5 (start_tls with OpenLDAP 2.0.x) is not working ...
- Re patch for 2.2.5 and check for start_tls with OpenLDAP 2.0.x libs
- patch for 2.2.5 and check for start_tls with OpenLDAP 2.0.x libs