Re: Update

On 20/05/2019 20:01, Kurt Roeckx wrote: > On Mon, May 20, 2019 at 10:21:45AM -0700, Paul Yang wrote: >> >> The Chinese modified TLS protocol is not intended to interoperate with any >> other TLS protocols. The cipher suites defined in this protocol should not >> be used with the standard IETF

RE: Welcoming our new committers

Welcome to the team. Pauli -- Oracle Dr Paul Dale | Cryptographer | Network Security & Encryption Phone +61 7 3031 7217 Oracle Australia -Original Message- From: Matt Caswell [mailto:m...@openssl.org] Sent: Monday, 20 May 2019 8:31 PM To: openssl-project@openssl.org Subject: Welcomin

Re: Update

On Mon, May 20, 2019 at 10:21:45AM -0700, Paul Yang wrote: > > The Chinese modified TLS protocol is not intended to interoperate with any > other TLS protocols. The cipher suites defined in this protocol should not be > used with the standard IETF TLS. So I guess what Matt said would be feasible

Re: Update

> On May 20, 2019, at 07:49, Matt Caswell wrote: > > > On 20/05/2019 15:23, Salz, Rich wrote: >>> I don't see it that way. As I understand it this is a completely different >>protocol to standard TLS. >> >> That's an interesting point, but ... they use the SSL "name." > > Which isn't e

Re: Update

On 20/05/2019 15:23, Salz, Rich wrote: >>I don't see it that way. As I understand it this is a completely different > protocol to standard TLS. > > That's an interesting point, but ... they use the SSL "name." Which isn't even an IETF name...the IETF call it TLS ;-) >> It is not intende

Re: Update

>I don't see it that way. As I understand it this is a completely different protocol to standard TLS. That's an interesting point, but ... they use the SSL "name." > It is not intended to interoperate with it in any way. Is that true? I didn't look closely at the protocol changes, but m

Re: Update

On Mon, 20 May 2019 16:05:49 +0200, Salz, Rich wrote: > > * The current requirement for inclusion is “national standard” or better. > Thus, this change > should be accepted. > > The problem is that they squatted on codepoints that the IETF controls. So > while it is a national > standar

Re: Update

On 20/05/2019 15:05, Salz, Rich wrote: > > The problem is that they squatted on codepoints that the IETF controls. So > while it is a national standard, it is also in conflict with the IETF > specifications. > I don't see it that way. As I understand it this is a completely different proto

Re: Update

* The current requirement for inclusion is “national standard

Welcoming our new committers

Please welcome our four new committers as announced here: https://www.openssl.org/blog/blog/2019/05/20/committers/ The new committers are: Dmitry Belyavsky, Shane Lontis, Tomáš Mráz and Patrick Steuer. Welcome all! Matt