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

Summary:	Error loading certificate file containing negative serial number
Product:	Red Hat Enterprise Linux 7	Reporter:	Jordan Liggitt <jliggitt>
Component:	golang	Assignee:	Jakub Čajka <jcajka>
Status:	CLOSED ERRATA	QA Contact:	Martin Cermak <mcermak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	carl, mcermak, mnewsome
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	golang-1.6-1.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:	1289473
Clones:	1290543 (view as bug list)		Environment:
Last Closed:	2016-11-04 01:35:08 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:
Bug Blocks:	1289473

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