Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1011083 - CA certificate cannot be specified by nickname [documentation bug]
CA certificate cannot be specified by nickname [documentation bug]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: curl (Show other bugs)
6.4
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Kamil Dudka
Stefan Kremen
: Documentation
Depends On: 905066
Blocks: 1188327
  Show dependency tree / graph
 
Reported: 2013-09-23 11:15 EDT by Peter Schiffer
Modified: 2015-07-22 01:43 EDT (History)
3 users (show)

See Also:
Fixed In Version: curl-7.19.7-43.el6
Doc Type: Bug Fix
Doc Text:
Previously, the curl.1 and curl_easy_setopt.3 man pages provided incorrect information about loading CA certificates. The --cacert option of curl (and CURLOPT_CAINFO option of libcurl) can only be used to specify CA certificates from files, which is now correctly stated in the man pages.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-22 01:43:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1254 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2015-07-20 13:50:03 EDT

  None (edit)
Description Peter Schiffer 2013-09-23 11:15:12 EDT 
This is a clone of original report: bug #905066.
The description of problem is contained in the original bug report.
Comment 9 errata-xmlrpc 2015-07-22 01:43:06 EDT 
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/RHSA-2015-1254.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.