[20.10 FEAT] openssl: RNG support

[bugproxy]

Provide a CPACF based random number generator for openSSL using PRNO-SHA-512-DRNG to implement a NIST SP800-90A compliant SHA512 hash based deterministic random bit generator (DRBG) seeded true random numbers extracted using the PRNO-TRNG instruction.

Planned with > openssl 1.1.1

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-11-19 09:10 EDT-------
Move Target to 19.10.

[Frank Heimes (fheimes)]

updating title

[Launchpad Janitor (janitor)]

[Expired for Ubuntu on IBM z Systems because there has been no activity for 60 days.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-04-25 08:01 EDT-------
This LP is in expired date, but should be active again for 19.10

[Andrew Cloke (andrew-cloke)]

Moved back to triaged.

[Frank Heimes (fheimes)]

Which is the target release of of openssl (it just says >1.1.1) this is going to land?
Just to make sure that it's available in time for the 19.10 development.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-04-30 09:27 EDT-------
Feature will be provided with openssl 3.0

[Frank Heimes (fheimes)]

Changing to Incomplete until OpenSSL 3.0 is released.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-07-08 10:46 EDT-------
Moved target from 19.10 -> 20.04 . Feature will not make it in time...

[Frank Heimes (fheimes)]

Changing title and status to Incomplete until development of target Ubuntu release starts.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu on IBM z Systems because there has been no activity for 60 days.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-01-30 08:46 EDT-------
Feature will not make it in time for 20.04 -> New target 20.10

[Dimitri John Ledkov (xnox)]

OpenSSL 3 is due to release in Q4 of 2020. I do not expect to ship OpenSSL 3 in 20.10.

New target 21.04 ?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-08-27 07:32 EDT-------
@Frank: Please check if
commit https://github.com/openssl/openssl/commit/53eb05bdf00d7237e3b12976c2ac38d68206eb13

is applied to your openssl 1.1.1. This will implement the feature.

Many thx

[Frank Heimes (fheimes)]

No, it doesn't look like patch "AES CTR-DRGB: performance improvement" (53eb05bdf00d7237e3b12976c2ac38d68206eb13) is in groovy's 1.1.1f-1ubuntu3.

[Dimitri John Ledkov (xnox)]

Why is this comment appearing after the feature freeze, instead of in march when it was implemented on the master branch? Or april when promoted about this. Or may when it was cherrypicked to stable upstream release.

Was there anything that canonical could have done, to have this identified & ship earlier?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-09-04 06:13 EDT-------
@Xnox. Sorry for this late update. I falls thru the cracks in my side.
But is this still possible, to get in into 20.10. That would really appreciated.
Many thanks in advance.....

[Dimitri John Ledkov (xnox)]

The patch mentioned alone does not apply on 1.1.1f in Ubuntu, it seems it also needs

9cc834d966ea5afc38fb829bfe498aed4c5d498d
0d011f540400b425aba1c3e59624ad9dbabe83cb
a1ec85c169a8e53e52ab35914ad47b5baea84070
53eb05bdf00d7237e3b12976c2ac38d68206eb13
e6a80cbad28ee748830815634917efe96948f2f3

Will try this set next.

[Launchpad Janitor (janitor)]

This bug was fixed in the package openssl - 1.1.1f-1ubuntu4

---------------
openssl (1.1.1f-1ubuntu4) groovy; urgency=medium

  * Cherrypick upstream fix for non-interactive detection on Linux. LP:
    #1879826
  * Cherrypick AES CTR-DRGB: performance improvement LP: #1799928
  * Skip services restart & reboot notification if needrestart is in-use
    LP: #1895708

 -- Dimitri John Ledkov <email address hidden> Tue, 15 Sep 2020 18:04:36 +0100

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-09-22 02:05 EDT-------
IBM Bugzilla status->closed, Fix Released with groovy