On Thu, Jul 23, 2015 at 12:56:50PM +0200, Lukas Slebodnik wrote:
On (23/07/15 11:51), Jakub Hrozek wrote:
>On Thu, Jul 23, 2015 at 10:30:54AM +0100, John Beranek wrote:
>> So, RHEL 6.7 has been released, but I was surprised at the version
>> contained in it:
>That's a relict of how RHEL works. You can only put a new tarball until
>a certain point, then you're only allowed to add patches that address a
>specific problem or RFE. That guarantees a certain level of stability.
>The -47 is "patch number", which means 47 bugs addressed atop 1.12.4. (I
>normally use a patch number per bugzilla..)
>> Does this version have the important fixes in it? I thought 1.12.5 was
>1.12.4-47 in RHEL ~= 1.12.5 upstream
>Actually here is a diff between my git branch that tracks rhel-6.7 and
>the upstream sssd-1-12 branch:
> < d119324 Updating version for the 1.12.6 release
> < 40f1824 Updating translations for the 1.12.5 release
> < 45429eb PROXY: Do not register signal with SA_SIGINFO
> < d3ff187 PROXY: proxy_child should work in non-root mode
> < c494e10 krb5: new option krb5_map_user
> < d788ec2 libwbclient-sssd: update interface to version 0.12
> < 1590f8d LDAP: warn about lockout option being deprecated
> < 39e33e3 SDAP: use DN to update entry
> < fec528a LDAP: return after tevent_req_error
I hope this missing patch will not cause a troubles in rhel6.
setenv() is very unlikely to fail.
We had a similar bugs an it caused use-after free and then crash.