Bug 1382094 - libtasn1 doesn't handle OIDs which have elements of size which exceed 32-bits
Summary: libtasn1 doesn't handle OIDs which have elements of size which exceed 32-bits
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libtasn1
Version: 6.8
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1330753
Blocks: 1323644
TreeView+ depends on / blocked
 
Reported: 2016-10-05 17:33 UTC by Hubert Kario
Modified: 2017-10-24 12:44 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1330753
Environment:
Last Closed: 2017-10-24 12:44:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1353838 0 unspecified CLOSED libtasn1 doesn't handle OIDs which have elements of size which exceed 32-bits 2021-02-22 00:41:40 UTC

Description Hubert Kario 2016-10-05 17:33:21 UTC 
+++ This bug was initially created as a clone of Bug #1330753 +++

Description of problem:

I am unable to access an ostree repository with the certs we generate, but I am able to access it with curl with those certs. I am also able to access it with different certs (I will attach both)

The error message is -- error: Server required TLS certificate

Version-Release number of selected component (if applicable):

ostree 2016.1
  +libsoup +gpgme +libarchive +selinux

How reproducible:

Always

Steps to Reproduce:
I will give instructions to reproduce it in a production server of Satellite in a private comment below.

Actual results:

I am restricted from accessing the repo

Expected results:

The certs work on the repo
Comment 1 Nikos Mavrogiannopoulos 2016-10-06 14:13:28 UTC 
Is that something that we need to address in RHEL6.9? (i.e., does it affect satellite?).
Note You need to log in before you can comment on or make changes to this bug.