Previously, we only handled KRB5KRB_AP_ERR_SKEW which meant that if krb5_child received KRB5_KDCREP_SKEW, SSSD returned System Error.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=889206#c4 and the next two comments.
On Wed, Jan 14, 2015 at 11:50:39AM +0100, Jakub Hrozek wrote:
Previously, we only handled KRB5KRB_AP_ERR_SKEW which meant that if krb5_child received KRB5_KDCREP_SKEW, SSSD returned System Error.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=889206#c4 and the next two comments.
ACK
bye, Sumit
On Wed, Jan 14, 2015 at 01:04:56PM +0100, Sumit Bose wrote:
On Wed, Jan 14, 2015 at 11:50:39AM +0100, Jakub Hrozek wrote:
Previously, we only handled KRB5KRB_AP_ERR_SKEW which meant that if krb5_child received KRB5_KDCREP_SKEW, SSSD returned System Error.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=889206#c4 and the next two comments.
ACK
bye, Sumit
* master: 9b2cd4e5e451c07cb2f04cdbaea2b94ccb5fb2ee * sssd-1-12: f5c3dcc3701e203f17a2803ff5019b853b4d7bee
sssd-devel@lists.fedorahosted.org