Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 878969

Summary: Write replacement for python-crypto
Product: Red Hat Enterprise Linux 6 Reporter: Rob Crittenden <rcritten>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.4CC: 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 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3271

python-crypto is not available in some distributions. We use Crypto.Cipher.ARC4 for AD trusts as trust is established with authentication blob encrypted with RC4.

A replacement will need to be written, one candidate being to extend the python-krbV to add a crypto interface.
Comment 1 Rob Crittenden 2012-11-21 16:54:21 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.
Comment 2 Rob Crittenden 2012-11-21 17:06:02 UTC 
Patch pushed upstream.

master: 7960b5c67f0577e305d9fd86564b19957872d0e3

ipa-3-0: 683eca02b43d0405422928e00f79049d054bfeb0
Comment 4 Martin Kosek 2012-12-19 17:20:25 UTC 
ipa-server-trust-ad Requires were fixed in ipa-3.0.0-17.el6. (python-crypto requirement was replaced with m2crypto requirement).
Comment 6 Namita Soman 2013-01-29 00:31:41 UTC 
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)
Comment 8 errata-xmlrpc 2013-02-21 09:30:44 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, 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