Date: Wed, 23 Oct 2019 18:28:32 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241347] security/sssd: Update to 1.16.4 Message-ID: <bug-241347-7788-MF0yUO313m@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241347-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-241347-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241347 --- Comment #10 from Phillip R. Jaenke <prj@rootwyrm.com> --- > I would probably need to update port to not rely on pyhton3 but directly = use python3.6. Is that what you want? Definitely not; I just saw the python2 and was worried it might be attempti= ng to use that. ports should still have 3.4+ for quite some time, so the flavo= rs method (and SHEBANGFIX) that Rick mentioned would be the best way there. > Do I understand that you worry about mixing MIT krb5 and heimdal when bui= lding with samba ? Yes, this is a known issue we ran into back on 1.13 when it was working cle= anly if you don't recall. By default, FreeBSD samba4x uses the built-in Heimdal = due to AD_DC being a default option. So a user taking samba48 or samba410 from pkg.freebsd.org and building security/sssd locally will end up with a broken sssd. samba48+ now has the option for MIT due upstream updates, but it's a non-default option on FreeBSD. So some additional care needs to be taken in= the context of FreeBSD. Basically the security/sssd port should tell the user t= hat the MIT option is required on their samba48 or samba410. > The tricky part is winbind_idmap_sss.so The might change ABI between vers= ions and thus you need to recompile the plugin and to "downgrade" version with --with-smb-idmap-interface-version=3D6 > 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 I would argue that it is a LOT more dangerous to NOT have the AD provider. I don't think the IPA provider is going to work correctly anyways (but it has been a while and I don't have a test environment handy.) But the AD provide= r is basically the number one use case on FreeBSD. So not having it working is g= oing to be a LOT worse than people having Samba without MIT kerberos. The Samba API changes absolutely make it a challenge and a half though, ESPECIALLY because net/samba410 is Schroedinger's Port: both broken and working. And both with built-in ldb and ldb1.5 (I think, I'd have to look again.) And in a lot of flux because AD_DC provisioning is broken plus folks attempting to fix it on ZFS again. That really throws a wrench into the wor= ks.=20 Rick, do you know of an approved or at least not-horrible way to do CONFIG+=3D--with-smb-idmap-interface-version=3D6 based on the DEFAULT_VERSI= ONS value for samba? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241347-7788-MF0yUO313m>