On Wed, 2017-05-31 at 15:41 +0200, Lukas Slebodnik wrote:
On (31/05/17 12:45), Joakim Tjernlund wrote:
> On Wed, 2017-05-31 at 10:54 +0200, Jakub Hrozek wrote:
> > On Wed, May 31, 2017 at 10:09:26AM +0200, Lukas Slebodnik wrote:
> > > On (31/05/17 08:19), Lachlan Musicman wrote:
> > > > Hi all,
> > > >
> > > > I noticed a while ago that 1.15.3 was versioned in the repo but
I've not
> > > > seen anything released? I'm mostly looking on the COPR
> > > > (
> > > >
https://pagure.io/SSSD/sssd/c/012ee7c3fe24a5e75d9b0465268c1bb8187b8337?br...
> > > > )
> > > >
> > >
> > > Version is immediately increased in git to simplify life for developers.
> > > 1.15.3 is still a devel version and not official.
> > >
> > > BTW 1.15.2 is in copr for some time
> > >
https://copr.fedorainfracloud.org/coprs/g/sssd/sssd-1-15/
> > >
> > > > This is purely selfish - I love all that you do, and I'm aware
that there
> > > > has been some fairly comprehensive infrastructural change.
> > > >
> > > > I'm just waiting on that one fix and have no roadmap visibility
:)
> > > >
> > >
> > > Which fix do you mean?
> >
> > I suspect it's #3382 -- this bug hit quite a few people, do you think
> > it's a good idea to regenerate the copr with 1.15.2 and this fix?
> >
> > on the other hand, 1.15.3 is not far away (promise :-))
>
> Could you deal with(Quoting earlier mail below) before 1.15.3 too? Fix could be as
simple
> as reverting just KRB5KRB_AP_ERR_TKT_EXPIRED, works fine here.
>
Reverting fix your use-case.
But it will break
https://pagure.io/SSSD/sssd/issue/3174
no, that is not how I read that issue, his problem was time skew and related to
KRB5KRB_AP_ERR_TKT_NYV and would never had happened if the clock was correct to begin
with.
KRB5KRB_AP_ERR_TKT_EXPIRED was thrown in for good measure.
So reverting KRB5KRB_AP_ERR_TKT_EXPIRED is the correct fix for both I think.
I am not sure whether I mentioned it in different thread but this bug is
tracked in
https://pagure.io/SSSD/sssd/issue/3406
OK, thanks.