Bug 745242
Summary: | Fallback to import the private keys as PKCS#8 if regular import fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Erinn Looney-Triggs <erinn.looneytriggs> |
Component: | gnutls | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Jaburek <jjaburek> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | CC: | jjaburek, theinric |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gnutls-2.8.5-8.el6 | Doc Type: | Enhancement |
Doc Text: |
Feature:
GNUTLS now allows loading also private keys in PKCS#8 format if application calls gnutls_x509_privkey_import().
Reason:
If a private key is in the PKCS#8 format applications which use gnutls_x509_privkey_import() would previously fail to load it.
Result (if any):
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:33:09 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: | 772279, 782183, 836160, 840699 |
Description
Erinn Looney-Triggs
2011-10-11 18:41:59 UTC
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This is the gnutls commit for reference: http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=commitdiff;h=f780425c751c6e31d26985e629d1abf3886168d3;hp=1d303703e4f4ab16b090d4506c68be5476ecb376 The core dump must be solved on the rsyslog side. Also please use the regular support channels to request the bug to be fixed. It is necessary for proper prioritizing. Case #00513502 has been open for two months before I finally gave up and opened this BZ. Hopefully this will allow you to prioritize etc. -Erinn The core dump fix is the bug 727380 for reference. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. *** Bug 798054 has been marked as a duplicate of this bug. *** Ha, forgot I filed this bug, so filed another one. Ah, how funny. -Erinn 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/RHBA-2013-0425.html |