Bug 144830 - Add Wells Fargo Root Certificate Authority to ca-bundle.crt
Summary: Add Wells Fargo Root Certificate Authority to ca-bundle.crt
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openssl (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: All Linux
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Brian Brock
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-11 20:18 UTC by Ryan Koski
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-08 15:57:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ryan Koski 2005-01-11 20:18:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
Wells Fargo would like to have the Wells Fargo Root Certificate
Authority certificate added to the ca-bundle.crt file included with
the openssl RPM on RedHat and Fedora distributions.

The actual certificate will be communicated via a digitally signed
email upon request.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install the openssl RPM
2. Notice that the Wells Fargo Root Certificate Authority cert is not
in the ca-bundle.crt.


Additional info:

Comment 1 Suzanne Hillman 2005-01-12 20:34:14 UTC
Internal RFE bug #144935 entered; will be considered for future releases.

Comment 2 Joe Orton 2005-02-04 16:08:46 UTC
The policy for managing the OpenSSL "ca-bundle.crt" is to keep it in
synch with the Mozilla root CA list.  Once the certificate has been
approved for inclusion in the Mozilla list, it will automatically be
pulled into the openssl package for a future release.

Requests for inclusion in the Mozilla CA root list can be filed here:


Comment 3 Tomas Mraz 2005-09-08 15:57:13 UTC
See comment #2.

This problem will be resolved in a future major release of Red Hat Enterprise
Linux. Red Hat does not currently plan to provide a resolution for this in a Red
Hat Enterprise Linux update for currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects. 

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