alexmgr

Hi @martind1111, `Scapy-ssl_tls` only supports TLS 1.3 draft 18, until I find time to implement the final spec. That change (having the server use `TLSExtSupportedVersions` instead of the SH `version`...

+2 on this proposal, makes a clear distinction between TLSContext and keys. We probably want TLSKeyStore properties to be settable only once, when a user specifies the TLSKeyStore explicitely. This...

Hi, I thought scapy wasn't python3 compatible until I saw your fork. Nice work! Since you have obvious experience with the transition process, do you have a rough idea of...

Thanks for the information. Six package seems to allow some abstraction types for this use case. I think we don't want to maintain multiple branches. I'll give it some more...

Hi @MichaelLiuzzi, Sorry for the late answer. Nothing really happened on this. Anyone here interested in picking this up?

Thanks for the heads up @cniemira, If you have some time to move this forward, could you work on top of the `tls1.3` branch? Appreciate the help, Alex

Hi, For the most part this should work out of the box. Do something like that: ``` python pkt = TLSRecord() / TLSHandshake() / TLSClientHello(version=TLSVersion.TLS_1_2, extensions=[TLSExtension() / TLSExtRenegotiationInfo()]) with TLSSocket(socket.socket(),...

Hi @mukundamj, #73 has been merged. I'll have a look into addressing this. You can follow progress on renegotiation branch if interested. Alex

OK, so this is way more complicated then I initially thought. I've got this working until the second symmetric encryption kicks in. So master-secret and symmetrical keys are re-negotiated OK....

Hey @tintinweb, Didn't look into this, might be negotiating another draft version then what we have (18). Don't have much time right now, might disable the test?