On Fri, 2019-12-27 at 19:21 +0000, David Woodhouse wrote: > Read 3580 bytes of IF-T/TLS EAP-TTLS record > < 0000: 00 00 55 97 00 00 00 05 00 00 0d fc 00 00 01 f8 |..U.............| > < 0010: 00 0a 4c 01 01 03 0d e8 15 c0 00 00 0e 35 16 03 |..L..........5..| > > > From the c0 00 00 0e 35 ... on the second line is the EAP-TTLS. > > See https://tools.ietf.org/html/rfc5281#section-9.1 — that first byte > has the L and M bits set indicating that the TLS frame is (entirely > gratuitously) fragmented. I haven't implemented fragmentation yet as > I hadn't seen it in the wild and there's no point in it. Should be > simple enough... First, somewhat rushed, attempt at https://gitlab.com/openconnect/openconnect/commits/ttlsfrag Please let me know if it works.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
