On 04/03/18 16:30, Kurt Roeckx wrote:
> On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote:
>> I also intend to merge the config file .include PR (5351), and I want us to
>> decide about 4848.
>
> I have to agree that I want to resolv 4848 (reading config file to
> select things like su
Am 04.03.2018 um 17:30 schrieb Kurt Roeckx:
> There is also still work going on related to the DRBG API.
Kurt convinced me that the DRBG backend (the reseeding) needs some
adjustments in order to comply to NIST SP 800-90C. This applies in
particular to the prediction_resistance feature. And there
On Sun, Mar 04, 2018 at 05:30:32PM +0100, Kurt Roeckx wrote:
> On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote:
> > I also intend to merge the config file .include PR (5351), and I want us to
> > decide about 4848.
>
> I have to agree that I want to resolv 4848 (reading config file to
On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote:
> I also intend to merge the config file .include PR (5351), and I want us to
> decide about 4848.
I have to agree that I want to resolv 4848 (reading config file to
select things like supported ciphers.)
An other important change is re
I also intend to merge the config file .include PR (5351), and I want us to
decide about 4848. With new protocol verison and its required new ciphers
coming into this release, *now* is the time.
On 3/4/18, 9:39 AM, "Salz, Rich" wrote:
Kurt raises an excellent point.
I want this
Kurt raises an excellent point.
I want this in the release:
https://github.com/openssl/openssl/pull/5438
I want discussion about these two, hopefully concluding that they be in the
release:
https://github.com/openssl/openssl/pull/5326
https://github.com/openssl/openssl/pu
On Fri, Mar 02, 2018 at 11:09:30AM +, Matt Caswell wrote:
> Just a reminder, in case anyone missed it, that our next planned release
> on 13th March is beta1. This means we will be calling a feature freeze
> for 1.1.1 and we will create the new branch. If you've got any
> outstanding feature PR
Just a reminder, in case anyone missed it, that our next planned release
on 13th March is beta1. This means we will be calling a feature freeze
for 1.1.1 and we will create the new branch. If you've got any
outstanding feature PRs that you want in for 1.1.1 - then now is the
time to get them finish
