Bug 1360639 - update to libtasn1 4.x branch
Summary: update to libtasn1 4.x branch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libtasn1
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact: Stanislav Zidek
URL:
Whiteboard:
Depends On:
Blocks: 1377248
TreeView+ depends on / blocked
 
Reported: 2016-07-27 08:42 UTC by Nikos Mavrogiannopoulos
Modified: 2017-08-01 15:09 UTC (History)
4 users (show)

Fixed In Version: libtasn1-4.9-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase package(s) to version: 4.9 Highlights, important fixes, or notable enhancements: This rebase brings several decoding performance optimizations in libtasn1. It also brings features such simpler DER and BER decoding functions, as well as the ability to enforce strict DER compliance allowing safer decoding.
Clone Of:
Environment:
Last Closed: 2017-08-01 15:09:19 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1860 normal SHIPPED_LIVE Moderate: libtasn1 security, bug fix, and enhancement update 2017-08-01 17:50:00 UTC

Description Nikos Mavrogiannopoulos 2016-07-27 08:42:42 UTC
Description of problem:
The libtasn1 3.x branch is unmaintained upstream, and has several open security issues. The 4.x branch in addition to having these security issues resolved it contains several performance improvements (e.g., parsing time of a 10mb crl from minutes to a second), that warrant upgrading to it.

Comment 10 errata-xmlrpc 2017-08-01 15:09:19 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://access.redhat.com/errata/RHSA-2017:1860


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