Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Sep 2023 20:35:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 247940] Introduce gssapi=.. in DEFAULT_VERSIONS like for ssl=...
Message-ID:  <bug-247940-7788-vu4wUMSvbR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-247940-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-247940-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=3D247940

Joseph Mingrone <jrm@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jrm@freebsd.org

--- Comment #5 from Joseph Mingrone <jrm@freebsd.org> ---
Michael,

tl;dr I don't think using Mk/bsd.default-versions.mk for building ports with
different Kerberos implementations is feasible.

For the default versions feature to make sense, we need ports to have
USES=3Dgssapi without specifying a Kerberos implementation.  That way, a va=
lue
set for DEFAULT_VERSIONS+=3Dgssapi=3D can be used, or if that isn't set, we=
 can
fall back to the default of using Kerberos from base.  However, this isn't =
how
our 58 ports with USES=3Dgssapi currently work.

Twelve ports have USES=3Dgssapi without an OPTION, but they all hardcode the
Kerberos implementation.

Of the remaining ports, the ones that have OPTION knobs for all of the Kerb=
eros
implementations could, in theory, be converted to use a default version, but
there are complications.  For example, many of them require different confi=
gure
flags.  For example, here is what we have in
security/cyrus-sasl2-gssapi/Makefile

GSSAPI_HEIMDAL_USES=3D     gssapi:heimdal,flags
GSSAPI_HEIMDAL_CONFIGURE_ON=3D    --enable-gssapi=3D"${GSSAPIBASEDIR}" \
                         --with-gss_impl=3Dheimdal

but other ports like security/samba416 have

GSSAPI_HEIMDAL_CONFIGURE_ON=3D    --with-system-heimdalkrb5 ${GSSAPIBASEDIR}
GSSAPI_HEIMDAL_USES=3D     gssapi:heimdal
GSSAPI_HEIMDAL_PREVENTS=3D    AD_DC
GSSAPI_HEIMDAL_PREVENTS_MSG=3D    GSSAPI_HEIMDAL and AD_DC enable conflicti=
ng
options

A workaround is to specify something like this in /etc/make.conf.

.if ${.CURDIR:M*/net/samba*}
WITHOUT=3DGSSAPI_BUILTIN
WITH=3DGSSAPI_MIT
.endif

You still have to think about individual ports, but at least you can share =
this
configuration between systems, and you won't have to go through the
configuration dialogs manually.

I hope this helps.

Joe

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247940-7788-vu4wUMSvbR>