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 1167471

Summary: [RFE] Provide Tomcat support for TLS v1.1 and TLS v1.2 (Tomcatjss)
Product: Red Hat Enterprise Linux 6 Reporter: Nathan Kinder <nkinder>
Component: tomcatjssAssignee: Christina Fu <cfu>
Status: CLOSED ERRATA QA Contact: Asha Akkiangady <aakkiang>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: medium    
Version: 6.6CC: aakkiang, arubin, cfu, mharmsen, nhosoi, nkinder, rpattath, rrelyea
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tomcatjss-2.1.0-4.el6 Doc Type: Enhancement
Doc Text:
tomcatjss supports TLS versions 1.1 and 1.2 Tomcat has been updated to support the Transport Layer Security cryptographic protocol version 1.1 (TLSv1.1) and Transport Layer Security cryptographic protocol version 1.2 (TLSv1.2) using Java Security Services.
Story Points: ---
Clone Of: 871171 Environment:
Last Closed: 2015-07-22 06:28:53 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: 816396, 871171, 1167470    
Bug Blocks: 1171848, 1175494    
Attachments:
Description Flags
Patch to fix TLS issues none

Comment 1 Matthew Harmsen 2015-02-13 18:19:21 UTC
Created attachment 991464 [details]
Patch to fix TLS issues

Comment 3 Roshni 2015-04-15 16:57:00 UTC
[root@ipaqa64vmh tmp]# rpm -qi tomcatjss
Name        : tomcatjss                    Relocations: (not relocatable)
Version     : 2.1.0                             Vendor: Red Hat, Inc.
Release     : 4.el6                         Build Date: Sat 14 Feb 2015 10:58:41 AM EST
Install Date: Thu 09 Apr 2015 12:46:30 PM EDT      Build Host: x86-026.build.eng.bos.redhat.com
Group       : System Environment/Libraries   Source RPM: tomcatjss-2.1.0-4.el6.src.rpm
Size        : 46787                            License: LGPLv2+
Signature   : RSA/8, Wed 04 Mar 2015 07:34:24 AM EST, Key ID 938a80caf21541eb
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://pki.fedoraproject.org/
Summary     : JSSE implementation using JSS for Tomcat

Verification steps as described in https://bugzilla.redhat.com/show_bug.cgi?id=871171#c41. The setupssl2.sh script needed a modification, remove the following lines:

replace: sslVersionMin
sslVersionMin: TLS1.1
-
replace: sslVersionMax
sslVersionMax: TLS1.3

"<nhosoi> rpattath, on rhel-6.7, 389-ds-base enables TLS1.0 and newer by default."

Additional tests were performed as follows:

1. curl -E "CA_agent:276347752307" --basic -d "serialNumber=0x06" -k "https://<ca-host>:9443/ca/agent/ca/displayBySerial"

9443 is the secure port and the information about the cert was displayed.

Executed the same curl request with ssltap port 1924 when ssltap was running (ssltap -sxl <cs host>:<ca https port>)

2. Tested higher range of TLS
3. Also executed HttpClient -> CA as explained in https://bugzilla.redhat.com/show_bug.cgi?id=1040640#c5

Comment 5 errata-xmlrpc 2015-07-22 06:28:53 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.

https://rhn.redhat.com/errata/RHBA-2015-1316.html