> > For a more accurate and timely public overview over the current state of
> > the blockers,
> > it might be helpful to manage them via the 3.0.0 milestone
> >
> > https://github.com/openssl/openssl/milestone/15
> >
> > Some of the tickets listed below were already associated to the milestone,
On Fri, Sep 11, 2020 at 11:07:48AM +, Dr. Matthias St. Pierre wrote:
> For a more accurate and timely public overview over the current state of the
> blockers,
> it might be helpful to manage them via the 3.0.0 milestone
>
> https://github.com/openssl/openssl/milestone/15
>
> Some of the
by me now.
Just a suggestion.
Matthias
> -Original Message-
> From: openssl-project On Behalf Of Matt
> Caswell
> Sent: Thursday, September 10, 2020 1:24 PM
> To: openssl-project@openssl.org
> Subject: Re: Beta1 PR deadline
>
>
>
> On 10/09/
Shane has done the IG D.9 work: it is in #12835 and is awaiting review. I
think it should be in beta if possible. It’s mostly adding a second test case
due to NIST changing guidance recently, so low risk and helpful for the lab.
As Shane notes in 12801, there will be some conflicts generated
On 10/09/2020 11:40, Matt Caswell wrote:
>
>
> On 09/09/2020 13:03, Kurt Roeckx wrote:
>> On Wed, Aug 26, 2020 at 04:58:26PM +0100, Matt Caswell wrote:
>>> Please can anyone with PRs that they wish to have included in OpenSSL
>>> 3.0 beta1 ensure that they are merged to master by 8th
Hi Matt et al.,
thanks to good collaboration with OTC members I've been able to get approved
most of my open PRs that would be good be included before feature freeze,
while a few such PRs appear 'nearly' approved.
Given the 24-hours grace period, the PRs #12478
Hi Matt et al.,
thanks to good collaboration with OTC members I've been able to get approved
most of my open PRs that would be good be included before feature freeze,
while a few such PRs appear 'nearly' approved.
Given the 24-hours grace period, the PRs #12478
On 09.09.20 14:03, Kurt Roeckx wrote:
> On Wed, Aug 26, 2020 at 04:58:26PM +0100, Matt Caswell wrote:
>> Please can anyone with PRs that they wish to have included in OpenSSL
>> 3.0 beta1 ensure that they are merged to master by 8th September.
> So that date has passed now. Can someone give an
On Wed, Aug 26, 2020 at 04:58:26PM +0100, Matt Caswell wrote:
> Please can anyone with PRs that they wish to have included in OpenSSL
> 3.0 beta1 ensure that they are merged to master by 8th September.
So that date has passed now. Can someone give an overview of what
we think is still needed to
>Please can anyone with PRs that they wish to have included in OpenSSL
3.0 beta1 ensure that they are merged to master by 8th September.
And how are non-committers supposed to do that
On 26/08/2020 17:02, Salz, Rich wrote:
>>Please can anyone with PRs that they wish to have included in OpenSSL
> 3.0 beta1 ensure that they are merged to master by 8th September.
>
> And how are non-committers supposed to do that
>
In the same way as normal. Ensure your PRs are
It is also worth noting that new features will not be accepted during the beta
period.
Pauli
--
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations
Phone +61 7 3031 7217
Oracle Australia
> On 27 Aug 2020, at 1:58 am, Matt Caswell wrote:
>
> Hi all
>
> The OMC had a
Hi all
The OMC had a meeting today.
Please can anyone with PRs that they wish to have included in OpenSSL
3.0 beta1 ensure that they are merged to master by 8th September.
Note in particular that there is no PR at the moment to incorporate SM2
asymmetric encryption into OpenSSL 3.0. This
13 matches
Mail list logo
