Bug 2166109 - Backport PacRequestorEnforcement for adcli in RHEL6 [NEEDINFO]
Summary: Backport PacRequestorEnforcement for adcli in RHEL6
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: adcli
Version: 6.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-31 20:25 UTC by Daniel Filho
Modified: 2023-08-04 19:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-02 14:43:16 UTC
Target Upstream Version:
Embargoed:
pkettman: needinfo?
pkettman: needinfo?


Attachments (Terms of Use)

Description Daniel Filho 2023-01-31 20:25:55 UTC
Is possible to backport the following upstream correction to RHEL 6 adcli?

- https://gitlab.freedesktop.org/realmd/adcli/-/issues/27
- https://bugzilla.redhat.com/show_bug.cgi?id=2039349

Customer has little less than 1000 machines that they are not able to upgrade within the next year or so.

Comment 1 Sumit Bose 2023-02-01 07:11:17 UTC
Hi,

the fix for the two tickets you have mentioned is add some updates to the AD DCs, see 'Known Issues' section of https://support.microsoft.com/en-us/topic/kb5008380-authentication-updates-cve-2021-42287-9dafac11-e0d0-4cb8-959a-143bd0201041.

HTH

bye,
Sumit

Comment 2 Thorsten Scherf 2023-02-07 15:57:47 UTC
What Sumit said. Additionally please also see this KCS for a tl;dr of the Microsoft advisory:

Problem with Active Directory Join after KB5008380 
https://access.redhat.com/solutions/6633491

Comment 3 Thorsten Scherf 2023-02-07 16:01:37 UTC
And please also see the RHEL life-cycle document:

https://access.redhat.com/support/policy/updates/errata

"Red Hat Enterprise Linux 6 ELS delivers certain Red Hat defined Critical and Important security fixes and selected (at Red Hat discretion) urgent priority bug fixes and troubleshooting for the last minor release."


Note You need to log in before you can comment on or make changes to this bug.