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

Hubert Kario <[email protected]>
Newsgroups gmane.comp.mozilla.crypto
Message-ID <[email protected]>
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

-- 
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00  Brno, Czech Republic

-- 
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-----

iQIzBAABCgAdFiEEYeeuxEU+3unL/K+dkqjRuAHS9fUFAlwvhkEACgkQkqjRuAHS
9fWPGhAAmUHe538gSihEyBE6GK8S4M57BQMlMs4ohdvUasF9Cr0SWcY7hcVEhypV
ydDqR6lJKs9nLNRoK3gNE1HmYzZlMjeI4cdeUjjbfad05b4PWjeblJiVTHbGEooJ
fdcvna02ax9qEHOcMvxDGHMVPB9czMmkOjIAM+iuXHcOLyWEncjOjdk1hHoAPyKl
B184iOK88XPBrMQntCvR4NEWCZOSqToany3I8ea4jsrYbRq7Krr2zGatoMcqjRkM
R2tQBxlMRoGkN5MyrWez7dOa6K4viIEbdBeOH8+LE+sJ7SRHrNkapvp3WKByxayX
X/89SXTTIgRze8Mzv63O6pvIv0YavoOcBOn1KmsNSkK3WYOmSYvGNVQenrc0tVK3
6tM7kUc4Yexq763UmpVP8CIBNOJYz+8xfOLUs/Er0bwtwvbNBelk6C1OSwZckFpM
9A5iE51XWHWsd4wTwISku1lod3qxutUHJXct5LMbZCV1gmD3mWZq8z5rNj3ym/x3
n4obzkPOvH8Zw6IBLL2UNd5VfOGyrJj6VlfZPF+pgIxpIIWTIpKFMA0hI+2yX1iS
Wm4O2ce/6n1Qr1rgpxjkVY2TgHkIdCEUvkkIpYbwvK9K7a9EhLfT+qxxNwhV5g+v
w9/eJJzUsAtDq2xLPm+wwiMeM2hV2qK0zZPdbUDTtXwMqoLDi8k=
=RNip
-----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.