On Sun, Aug 30, 2015 at 12:03:47PM +0300, l(a)avc.su wrote:
> Hi Dmitri.
> I've got couple of evenings to follow your advice, and I have
> First of all, I've found out how SASL negotiates security of the
> context. In
> (just picks the max value both side can use)
> This bothered me the most, cause I need to understand how can I
> 'switching to plain' accidentally or on purpose. And it really could
> if someone set 'maxssf=1' in ldap.conf, so I just need to specify
> ldap_sasl_minssf=56 in sssd.conf, or SASL_SECPROPS minssf=56 in
You have to set minssf on the server-side to make sure that only
properly encrypted connections are accepted by the server, see e.g.
for an explanation how this can be done with the 389ds LDAP server.
On the client side SSSD by default use the settings from ldap.conf
is used by all other OpenLDAP based LDAP client programs as well. If
want to make sure that at least SSSD uses a secure connection you can
additionally set ldap_sasl_minssf in sssd.conf.
Thank you for the info. I've already set ldap_sasl_minssf in sssd.conf,
and in ldap.conf
Since I'm using Microsoft AD, I can't specify minssf on the server side.
I've found couple of corresponding parameters in ldap.conf that contols
Although any of combinations seems to have no effect on SSSD.
Thank you for the tip.