[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 #6 from lukas.slebodnik at intrak.sk ---
(In reply to Rick from comment #1)
> Reconsider defining an explicit Samba dependency. This factored into LDB conflicts between security/sssd and net/samba4* in the first place. Ports defines behavior for selecting the Samba version by setting a default that can be over-ridden via DEFAULT_VERSIONS, which puts greater control in the users hands.

Situation with LDB is different samba is more picky about version of ldb.
sssd can work without recompilation with ldb 1.2, 1.3, 1.4, 1.5
The only exception is ldb-1.1.30 due to ABI breakage in ldb.


> Explicit dependency mitigates current behavior, but when net/samba411 is added to ports and users want to install 4.11 as opposed to 4.10, it requires overriding SMB_LIB_DEPENDS instead of using DEFAULT_VERSIONS like "DEFAULT_VERSIONS=samba=4.11".

The tricky part is winbind_idmap_sss.so The might change ABI between versions
and thus you need to recompile the plugin and to "downgrade" version with
--with-smb-idmap-interface-version=6

Sure that module needn't be used by anyone and ipa and ad provider would work.
But it is dangeroups therefore I decided to stick with samna-4.10


> Addressing the current failing behavior is achievable through a note in Makefile or UPDATING explaining net/samba410 to be the minimum Samba version required for SMB support. So, users know to deploy a configuration similar to that described in bug #238465.


which changes do you suggest after my explanation?

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