Date: Mon, 21 Oct 2019 10:18:22 +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-H3Ir6bk3zy@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 #5 from lukas.slebodnik@intrak.sk --- (In reply to Phillip R. Jaenke from comment #3) > All that said, Lukas, can this build with python3.6+? FreeBSD is EOL'ing = 2.7 much more aggressively than RH. So I would recommend building only with= 3.x if possible so it doesn't come up as broken in January. My patch enforce python3 and disable python2 by default. Upstream tests python3.4+ so python3.6 should be fine I would probably need to update port to not rely on pyhton3 but directly use python3.6. Is that what you want? > The other concern I have is around the security/krb5 and samba dependency= . We don't have a good way to enforce option dependencies in other ports. I= think this can be worked around by depending on ${LOCALBASE}/lib/shared-mo= dules/krb5/winbind_krb5_localauth.so and ${LOCALBASE}/lib/samba4/krb5/plugi= ns/kdb/samba.so which are only present when GSSAPI_MIT is selected in samba= 48+. That SHOULD prevent user foot-shooting by installing a GSSAPI_BUILTIN = samba48+ against sssd here. Do I understand that you worry about mixing MIT krb5 and heimdal when build= ing with 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-H3Ir6bk3zy>