On Saturday, 13 January 2018 03:31:23 CET Christian Huitema wrote: > On 1/12/2018 1:53 PM, Dan Wing wrote: > > The question I want to ask: What can we do *now* to stop this from > > happening when TLS 1.4 will be deployed? I have the feeling GREASE > > won't be enough... > > Data sets. Machine learning algorithms are trained with data sets. If we > produce reference data sets showing what TLS 1.4 looks like, the vendors > can retrain their AI and start recognizing the new version for what it > is, rather than some unknown attack.
doesn't help with already deployed gear, and we really can't predict how TLS 1.4 will look like to give examples of it to them right now -- 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
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
