[Date Prev][Date Next]
Re: Enforce remote SSL/TLS
- To: email@example.com
- Subject: Re: Enforce remote SSL/TLS
- From: Kasper Loopstra <firstname.lastname@example.org>
- Date: Thu, 24 Nov 2011 15:53:46 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PwdAdbT4bWEndVYNmK+2JW3WH1k7eJ1JhGc70RZHB/Y=; b=XX7UPz8P2Dz0F23l/FbAdUXlSMePTsYFgY8CsfUK7WsqJhxNobUEJ39D1kb7A+I0eH BeZ1YB+L/yk25Ps5xUEaBPYo8DYj4WnNFonQLSbmiN5i6GDy/WIiOoEjGlo1dlcDbWsL xBXY7UNCbfln8ef/QY4N7V6iuBs0EvtwJBkVw=
- In-reply-to: <20111123165102.GC4524@dan.olp.net>
- References: <4ECD1A07.email@example.com> <20111123165102.GC4524@dan.olp.net>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20111004 Iceowl/1.0b1 Icedove/3.0.11
On 11/23/2011 05:51 PM, Dan White wrote:
On 23/11/11 17:06 +0100, Kasper Loopstra wrote:
We are using PAM to authenticate posixUsers against OpenLDAP. This
works great, and allows 'local' (ssh) logins. However, we also use
LDAP for a number of other services, including remote access and
editing via other software. This means we would like to keep our
users passwords as secure as possible, and enforce encrypted logins
for all remote hosts. However, PAM should still be able to
authenticate. The manner of encryption is not really important, it
just has to be strong enough to be useful over the internet, and
usable for all (or most) clients.
We have tried various solutions with ssf directives in
/etc/ldap/slapd.conf as well as the security tls=1 directive. All of
these attempts broke PAM.
Which PAM ldap module are you using? with PADL's module, you'd want to
configure 'ssl on' (for ldaps:///) or 'ssl starttls' (for starttls over
ldap:///) and also configure the tls_* settings appropriately.
We're using libpam-ldap from Debian, which is indeed the PADL module according to the comments. Is it really necesary to use SSL when communicating within localhost? If it is, that's fine, it just doesn't seem to be the right way to handle local traffic.
For your slapd configuration, see the slapd.conf manpage - the TLS*
options, as well as the 'security' option. If you are wishing to perform
secure connections over ldaps:///, verify that in your slapd init script,
that you are passing 'ldaps:///' as one of your '-h' command line
According to the init file provided by Debian, it seems to be using the conf file for this information. Is that correct/possible, or should we be asking the Debian people?
Thanks for the quick response,