Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-18 Thread Salz, Rich via openssl-users
This is factually incorrect; the TLS values are lower than the FIPS values, for example. And also, what “everyone in the know” has always stated isn’t really true any more. It would be nice to keep politics out of this list. -- openssl-users mailing list To unsubscribe: https://mta.openssl.or

Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-17 Thread Kyle Hamilton
gt; > > > Pauli > > -- > > Oracle > > Dr Paul Dale | Cryptographer | Network Security & Encryption > > Phone +61 7 3031 7217 > > Oracle Australia > > > > *From:* Dmitry Belyavsky [mailto:beld...@gmail.com] > *Sent:* Friday, 14 September 2018 8:41

Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-16 Thread Paul Dale
| Cryptographer | Network Security & Encryption Phone +61 7 3031 7217 Oracle Australia   From: Dmitry Belyavsky [mailto:beld...@gmail.com] Sent: Friday, 14 September 2018 8:41 PM To: openssl-users@openssl.org Subject: Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS   H

Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-14 Thread Dmitry Belyavsky
Hello, Sorry, I've just found similar checks in all _CGM functions. On Fri, Sep 14, 2018 at 1:30 PM Dmitry Belyavsky wrote: > Dear Paul, > > Could you please clarify? > The code seems to be related to s390 platform. Do I miss something? > > On Thu, Sep 13, 2018 at 1:55 AM Paul Dale wrote: > >>

Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-14 Thread Dmitry Belyavsky
Dear Paul, Could you please clarify? The code seems to be related to s390 platform. Do I miss something? On Thu, Sep 13, 2018 at 1:55 AM Paul Dale wrote: > I wasn’t aware of other national standards requiring a similar check. > > > > I made the change in the AES-GCM code because FIPS demands th

Re: [openssl-users] Limit the number of AES-GCM keys allowed in TLS

2018-09-12 Thread Paul Dale
I wasn’t aware of other national standards requiring a similar check.   I made the change in the AES-GCM code because FIPS demands the check be inside the FIPS boundary.  I’d have preferred to make it in the TLS layer, but that mustn’t be inside the FIPS boundary.  My understanding is that TLS