Simo Sorce <simo(a)redhat.com> writes:
> On Fri, 2017-03-10 at 12:56 +0200, Alexander Bokovoy wrote:
> > On pe, 10 maalis 2017, Lukas Slebodnik wrote:
> > > On (09/03/17 08:36), Simo Sorce wrote:
> > > > On Thu, 2017-03-09 at 13:49 +0100, Andreas Radke wrote:
> > > > > Am Thu, 09 Mar 2017 07:45:28 -0500 schrieb Simo Sorce <simo
> > > > > @redhat.com>:
> > > > >
> > > > > > Andreas, what krb5 implementation/version are you
> > > > > > building
> > > > > > gssproxy against ?
> > > >
> > > > Now looking at
https://www.archlinux.org/packages I see you
> > > > have an
> > > > outdate 1.13.7 version that does NOT have that stuff in
> > > > gssapi_krb5.h, but you also have 1.15.1 in staging, can you
> > > > try to
> > > > build against that version ?
> > >
> > > Then it would be good to bump minimal version of krb5-gssapi in
> > > configure.ac. It should fail at configure time IMHO.
> > >
> > >
https://pagure.io/gssproxy/blob/master/f/proxy/configure.ac#_11
> > > 7
> > >
> > > ATM there is 1.12.0. And I have no idea which is a minimal
> > > required
> > > version. Maybe 1.14.x which is in CentOS 7.3
> >
> > krb5 1.14 is where GSS_KRB5_CRED_NO_CI_FLAGS_X was introduced.
>
> Right, patch welcome :-)
Filed an issue:
https://pagure.io/gssproxy/issue/169
Note that krb5 upstream considers krb5 < 1.14 EOL anyway.