Bug 2076505

Summary: PAM Kerberos authentication incorrectly fails with a clock skew error
Product: Red Hat Enterprise Linux 8 Reporter: Pavel Filipensky <pfilipen>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED ERRATA QA Contact: Denis Karpelevich <dkarpele>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.7CC: aboscatt, asn, dkarpele, gdeschner, jarrpa, sssd-qe, tscherf
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: samba-4.15.5-7.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2076504
: 2078920 2079299 (view as bug list) Environment:
Last Closed: 2022-11-08 10:45:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2076504, 2078918    
Bug Blocks: 2078920, 2079299    

Description Pavel Filipensky 2022-04-19 08:43:59 UTC 
+++ This bug was initially created as a clone of Bug #2076504 +++

Description of problem:

From https://bugzilla.samba.org/show_bug.cgi?id=15046:

The samba testsuite has found that PAM Kerberos authentication can fail with an incorrect clock skew too great error. In the samba testsuite the server and the client run in the same machine.

The reason is that the time_offset passed to kerberos_return_pac() in winbindd_raw_kerberos_login() can be wrong. This time_offset is retrieved from an ADS_STRUCT directly casted from domain->private_data, when domain->private_data can point to a winbind_internal_pipes struct.

We have to remove the private_data field from winbindd_domain struct and use typed pointers.
Comment 7 errata-xmlrpc 2022-11-08 10:45:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (samba bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7698