On Monday, 5 September 2016 11:02:57 CEST Eric Rescorla wrote: > PR: https://github.com/tlswg/tls13-spec/pull/625 > > Currently the TLS spec requires implementations to send alerts under various > fatal conditions. However, many stacks actually don't send alerts
the only popular stack I found that does not seem to send alerts is the schannel from Microsoft F5, FortiOS, OpenSSL, NSS, GnuTLS, Java, mbedTLS, botan, axtls, Go implementation of TLS, all send alert messages > Note that these are to some extent orthogonal changes; even if we decide to > continue mandating sending alerts, that should be listed in one location not > scattered around the spec. In my opinion, putting the information how to handle errors in processing given message near the definition of a message makes it easier for implementers to implement and makes it less likely that they'll miss error handling. -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, 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
