Bug 878969
Summary: | Write replacement for python-crypto | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rob Crittenden <rcritten> |
Component: | ipa | Assignee: | Rob Crittenden <rcritten> |
Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | jgalipea, mkosek |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ipa-3.0.0-17.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 09:30:44 UTC | Type: | --- |
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: | |||
Bug Blocks: | 886216 |
Description
Rob Crittenden
2012-11-21 16:51:34 UTC
A very straightforward (read 2 or 3 lines) fix is to switch to use RC4 from M2Crypto. For QE purposes, this would be a regression-only test. AD trust cannot be established if this is not working. Patch pushed upstream. master: 7960b5c67f0577e305d9fd86564b19957872d0e3 ipa-3-0: 683eca02b43d0405422928e00f79049d054bfeb0 ipa-server-trust-ad Requires were fixed in ipa-3.0.0-17.el6. (python-crypto requirement was replaced with m2crypto requirement). Verified can add trust using ipa-server-3.0.0-22.el6.x86_64 # ipa trust-find --------------- 1 trust matched --------------- Realm name: adlab.qe Domain NetBIOS name: ADLAB Domain Security Identifier: S-1-5-21-3452862912-1583780823-338435951 Trust type: Active Directory domain ---------------------------- Number of entries returned 1 ---------------------------- # rpm -q --requires ipa-server-trust-ad | grep crypt m2crypto libcrypto.so.10()(64bit) libk5crypto.so.3()(64bit) libk5crypto.so.3(k5crypto_3_MIT)(64bit) 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html |