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.

=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:23 EDT
1. Feature Overview:
Feature Id:	[201744]
a. Name of Feature:	Cleanup of libICA Crypto library
b. Feature Description
The libica code is rather unreadable and has to be refactored.

2. Feature Details:
Sponsor:	zSeries
Architectures:
s390x

Arch Specificity: Purely Arch Specific Code
Affects Installer: Yes
Delivery Mechanism: Direct from community
Category:	Security
Request Type:	Package - Feature from IBM
d. Upstream Acceptance:	In Progress
Sponsor Priority	1
f. Severity: High
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	2.6.29

3. Business Case
The libica is a critical building block in the crypto stack. It needs to have a decent code quality
to keep it maintainable and extensible, providing a better serviceability for the customer.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, mgrf.com, Boeblingen 49-7031-16-3978

Technical contact(s):
Gonzalo Muelas Serrano, gmuelas.com

IBM Manager:
Thomas Schwarz, t.schwarz.com

I'm confused. libica is a userspace component (versioned at 1.3.x) - how is this targeted at 2.6.29?

Red Hat,

you are right, actually with:
IBM Bug 48096   -  RH Bug 462977 [LTC 6.0 FEAT] 201675:Pick up latest version of libica
this feature should be already included.

Sorry for the confusion,
Gonzalo Muelas Serrano.

When RHEL 6 takes libica version 2.0 this feature  is fulfilled

take latest from
http://sourceforge.net/project/showfiles.php?group_id=128009

libica 2.0.1 is built in Fedora - https://s390.koji.fedoraproject.org/koji/taskinfo?taskID=55752

*** This bug has been marked as a duplicate of bug 462977 ***