[Bug 241347] security/sssd: Update to 1.16.4

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241347

--- Comment #8 from lukas.slebodnik at intrak.sk ---
(In reply to Rick from comment #7)
> Comments to Makefile or UPDATING explaining and recommending defining default
> Samba to 4.10 when SMB is enabled are appropriate w/ the addition that changing
> the default may result in undesirable behavior as a consequence of differing
> ABIs with winbind_idmap_sss.so. This is irrelevant to me as each repository
> stands on it’s own.

That's not really true.
winbind_idmap_sss.so is plugin for winbind to use idmapping of SID -> (UIG/GID)
done by sssd. (samba and winbind use different algorithms)
And as I already mentioned the ABI for plugins is not very stable.
Therefore I decided to stick to samba 4.10

Sure the best would be more flexible and be able to build with 4.10 and 4.11
(cause one is in maintenance mode and another in stable release)
https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.11

But i would like to enforce strict runtime dependencies between samba and sssd.
Use the same version as were used at build time. And because of this I decided
to stick with samba 4.10 

Could you point me to other ports which have similar requirements
about build-time and run-time dependencies for different ports?

> Having said all that, sssd w/ the attached patch for 1.16.4 continues to fail
> during configure citing the error above. It occurs even despite defining
> PYTHON_VERSION and/or PYTHON_CMD in make.conf for either Python 2.7 or 3.6 like:
>
> .if ${.CURDIR:M*/security/sssd}
> PYTHON_VERSION= 3.6
> PYTHON_CMD=/usr/local/bin/python3.6
> OPTIONS_FILE_SET+=SMB  
> .endif

That is a different bug which will be addressed.

But I would like get an agreement about samba.

-- 
You are receiving this mail because:
You are the assignee for the bug.