Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1290472 - Error loading certificate file containing negative serial number
Summary: Error loading certificate file containing negative serial number
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: golang
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Čajka
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks: 1289473
TreeView+ depends on / blocked
 
Reported: 2015-12-10 15:43 UTC by Jordan Liggitt
Modified: 2016-11-04 01:35 UTC (History)
3 users (show)

Fixed In Version: golang-1.6-1.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1289473
: 1290543 (view as bug list)
Environment:
Last Closed: 2016-11-04 01:35:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2245 0 normal SHIPPED_LIVE golang bug fix update 2016-11-03 13:29:50 UTC

Description Jordan Liggitt 2015-12-10 15:43:11 UTC 
Description of problem:
x509 certificates containing negative serial numbers cannot be loaded.

Version-Release number of selected component (if applicable):
go 1.4.x, 1.5.x

How reproducible:
Always

Steps to Reproduce:
1. Create an x509 certificate with a negative serial number
2. Load it using golang's x509.ParseCertificate function

Actual results:
An error is returned

Expected results:
The certificate can be loaded

Additional info:
See https://github.com/golang/go/issues/8265

See http://play.golang.org/p/zpXKadV5mo for recreation
Comment 6 errata-xmlrpc 2016-11-04 01:35:08 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-2016-2245.html
Note You need to log in before you can comment on or make changes to this bug.