Bug 1660316 - [Intel 8.1 FEAT] Update openssl to latest version from the 1.1.1 branch
Summary: [Intel 8.1 FEAT] Update openssl to latest version from the 1.1.1 branch
Keywords:
Status: CLOSED DUPLICATE of bug 1643026
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssl
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.1
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1613905
TreeView+ depends on / blocked
 
Reported: 2018-12-18 06:56 UTC by Xiaolong Wong
Modified: 2019-01-16 10:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-16 10:25:13 UTC
Type: Feature Request
Target Upstream Version:


Attachments (Terms of Use)

Description Xiaolong Wong 2018-12-18 06:56:30 UTC
1.  Feature Overview:
a. Name of feature:
	Update openssl to latest
b. Feature Description:
	Update openssl to latest

2.  Feature Details:
a. Architectures: 64-bit Intel EM64T/AMD64
b. Bugzilla Dependencies: No
c. Drivers or hardware dependencies: N/A
d. Upstream acceptance information: Not submitted
e. External links: N/A
f. Severity (U,H,M,L): High (required for Hardware Enablement)

3. Business Justification:
a. Why is this feature needed?
b. What hardware does this enable? N/A
c. Forecast, impact on revenue? N/A
d. Any configuration info? N/A
e. Are there other dependencies? No

4. Primary contact at Red Hat, email, phone (chat)
	Xiaolong Wang  <xiaolwan@redhat.com>
  
5. Primary contact at Partner, email, phone (chat)
	Pragyansri Pathi <pragyansri.pathi@intel.com>

Comment 1 Tomas Mraz 2018-12-18 08:23:52 UTC
The plan is to update OpenSSL to the latest release from the 1.1.1 branch. There will not be an update to the master/3.0.0 release as it will not be ABI compatible with 1.1.1.

If any features from master are needed in RHEL-8, they will have to be properly backported.

Comment 2 Tomas Mraz 2019-01-16 10:25:13 UTC

*** This bug has been marked as a duplicate of bug 1643026 ***


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