On Wed, Dec 10, 2014 at 09:45:41AM +0100, Lukas Slebodnik wrote:
On (09/12/14 20:19), Jakub Hrozek wrote:
>On Sun, Dec 07, 2014 at 09:43:53PM +0100, Jakub Hrozek wrote:
>> On Sat, Dec 06, 2014 at 12:52:55PM +0100, Lukas Slebodnik wrote:
>> > On (05/12/14 14:22), Jakub Hrozek wrote:
>> > >Hi,
>> > >
>> > >since we released the last 1.9.x release today, I think it would be
>> > >prudent to also relase the 1.11.8 tarball so that 1.9.x users can
>> > >migrate to 1.11.x without being hit by known and fixed issues.
>> > >
>> > >Are there any fixes we'd like to see in the 1.11.8 release? I
propose
>> > >these two:
>> > > * 6a3ec7b LDAP: Do not clobber return value when multiple controls
are
>> > > returned
>> > > * fc8d98c SDAP: Deref needn't be treated as critical
>> > ^^^^^^^
>> > This patch was reverted in master
>> > @see 25dfb62595f73d1ca3d1170abe5853c4253d7c42
>>
>> oh well :-)
>>
>> thanks!
>
>I pushed 6a3ec7b from master to sssd-1-11 as
>d164404a2c5d6d5254b96567c7cda5e78a47f8bb
>
>Yesterday we learned than sssd segfaults for one user after upgrade from
>1.9 with the simples LDAP provider configuration with
>ldap_schema=rfc2307. We're going to wait a bit before releasing the
>1.11.8 tarball so that we can truly pronounce it LTM without any known
>regressions.
It seems that we have another candidate:
6e51d44a65b15c2f0491b0a8b452caac0bc00584
PAC: krb5_pac_verify failures should not be fatal
https://bugzilla.redhat.com/show_bug.cgi?id=1172494
Pushed to sssd-1-11 as: df62ac0be0ab00bb1661098590c2aec6773f321e