Would quic switch to openssl rather than boringssl after merge with TLS 1.3？

[Tinker Tan]

Hi,

such as the titile, i'm curios about that if quic crypto with TLS 1.3, then if it is possible to switch to use openssl?

[Ian Swett]

It should be possible, but it may require work since we intend to continue using BoringSSL in Chrome.

On Sun, Apr 28, 2019 at 5:44 AM Tinker Tan <tk10...@gmail.com> wrote:

Hi,

such as the titile, i'm curios about that if quic crypto with TLS 1.3, then if it is possible to switch to use openssl?

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[howard liao]

to push forward process of google QUIC to IETF standard, i strongly recommend that g QUIC should support openssl 1.3.  otherwise there is annoying symbol conflict problem occur to us when integrated g QUIC to https server (use http 1.3)

在 2019年4月29日星期一 UTC+8上午7:47:00，Ian Swett写道：

It should be possible, but it may require work since we intend to continue using BoringSSL in Chrome.

On Sun, Apr 28, 2019 at 5:44 AM Tinker Tan <tk10...@gmail.com> wrote:

Hi,

such as the titile, i'm curios about that if quic crypto with TLS 1.3, then if it is possible to switch to use openssl?

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to proto...@chromium.org.

[howard liao]

and i think the self-developed TLS stack in g QUIC should be not removed if introducing TLS 1.3  as you want to support both of them.

在 2019年5月23日星期四 UTC+8下午2:57:40，howard liao写道：

[Ryan Hamilton]

Google uses BoringSSL in our server and in Chrome. We have no plans to move away from BoringSSL in our QUIC code, but users of the code can probably swap in Openssl with some effort.

To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.

To post to this group, send email to proto...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/1fe06dfd-f838-4114-9e72-e001df7a30cb%40chromium.org.

[Nick Harper]

Where "some effort" is likely a lot of effort, given that BoringSSL has some QUIC-specific APIs that we use.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/CAJ_4DfQf7A5AgZ37KZH6cxeFWnnYQrVyzG4U%2Bavj85M%3D3VZp1g%40mail.gmail.com.