Re: TLS ESNI and HelloRetryRequest in Firefox 64, Firefox Nightly

[email protected]
Newsgroups gmane.comp.mozilla.crypto
Message-ID <[email protected]>
Is this already implemented?
[1] is not yet fixed and [2] does not work for me with current Nightly.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1494901
[2] https://www.cloudflare.com/ssl/encrypted-sni/


Am 04.01.19 um 17:13 schrieb Hubert Kario:
> On Thursday, 3 January 2019 11:45:25 CET Alexander Venedioukhin (lists) wrote:
>> Hello,
>>
>> I'm implementing ESNI (encrypted SNI, current draft 02) server-side.
>> It works with Firefox 64.0 and Nightly 66.0a1 as expected, until the
>> server sends HelloRetryRequest during handshake. In latter case
>> Firefox responds with plain text SNI extension (same hostname) in
>> second ClientHello, instead of ESNI. Still, handshake successfully
>> finishes. Is it intended behavior?
> 
> that sounds to me like a question to the IETF TLS mailing list
> 
>

-- 
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEf0BaT/qj9Rv+/e4vzoKyyG3Ou58FAlwvjhUACgkQzoKyyG3O
u5+PkQ/+PNa00LzFXDzVyt27+Q87JOfOSnIGlr7hlWlb7lYpzeuhDLGtRrMysIzM
69P6ZIoxxsHkgUWjVAmXbNwgva8daVaJyvU7CJjFXtr2wil2AXaTV3H/5RdOajYs
mCLf11ePeGWeVqAUeG1L/vBUuyvwg+VpNL0F9TKRd7vsEt7zn9bguct4iy9q1hlw
Fy7OwyPznCyxE3oM+at8WG7SdAXDfrQB7srAWsDxGQV6glmia1HTpRP5aM5WQH3G
merKPQaIWQl6GhhV0rRy8qMLeFwSvkueRDoCgoxQlTJib45zOqZySK2lEEdJD4BD
rBSyCaB+Nh48yh0HJDcKMBbCM7ySavM5XOshdIouf+Gc8+ZMV9WhudrkGQwCLv6x
qdMETRj1ahy0Khy/YSimk04MpQho23zwVUtcdsofuKL/V0n6rGSk2duXaJamHkUr
ZBml01yvy5sWbazXi0FaUhQHBUDp3HI4w6uRzYUChkP1/EyAuRjvk6S5+aYF5rbU
yDh/DQpxdGJQ3Fya9Zm9JfQTRrqRl5rpvAUfrbzMd/RHNRnszUY66MQfs9NNOkJk
jhL4cs14ewVNWOlOCdmu6AQe7484PgUiSWeaRkjtveb0qcu2pJOZ8y5lo1pd/PCp
JZn+hENcaffz800wVVzjIbodgjSh+Ikl3VJ/i/k5k3qtP2IBZPk=
=5tKt
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.