Bug 1152043 - Multiple ASN errors when generating certificates
Summary: Multiple ASN errors when generating certificates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xca
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Monnerat
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-13 11:53 UTC by Andreas Bierfert
Modified: 2014-11-01 16:47 UTC (History)
1 user (show)

Fixed In Version: xca-0.9.3-9.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-01 16:47:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Spec patch for f21/master (3.17 KB, application/mbox)
2014-10-13 11:53 UTC, Andreas Bierfert
no flags Details

Description Andreas Bierfert 2014-10-13 11:53:30 UTC
Created attachment 946349 [details]
Spec patch for f21/master

Multiple ASN errors when generating certificates due to changes in openssl 1.0.1i.

Patch attached.

Comment 1 Patrick Monnerat 2014-10-15 17:47:43 UTC
Thanks for pulling it to my attention.
Fixed in rawhide, will be in F21 soon.

Comment 2 Fedora Update System 2014-10-15 17:48:33 UTC
xca-0.9.3-9.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/xca-0.9.3-9.fc21

Comment 3 Fedora Update System 2014-10-16 17:18:55 UTC
Package xca-0.9.3-9.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xca-0.9.3-9.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12945/xca-0.9.3-9.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-11-01 16:47:38 UTC
xca-0.9.3-9.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


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