3 ms·
Notice this can't work if both clients and servers are, or could in future be, willing to use TLS 1.3 or later. In TLS 1.3 the Certificate message is encrypted
by tialaramex 5y ago
Notice this can't work if both clients and servers are, or could in future be, willing to use TLS 1.3 or later.
In TLS 1.3 the Certificate message is encrypted (as it perhaps always should have been) so this match won't work.
If you are responsible for all clients or servers on the path this netfilter applies to, you can choose to configure them to deliberately never use TLS 1.3 or later, and having done so this trick will "work" although it's non-compliant and anything can and will break it without notice.
If you don't have that control, you can't do anything about this. If you try to write a Netfilter that smashes TLS 1.3 negotiation hoping to trick one side into allowing TLS 1.2 you'll instead blow up the connection. This is deliberate, because if you could do this then there's no point in having better security in TLS 1.3.
- 1vuio0pswjnm7 5y agoI have been using TLS1.3 exclusively. I use a local forward proxy and I configure it to use 1.3 only for all outgoing connections. I have only discovered a few websites that do not yet support TLS1.3.
- tialaramex 5y agoThat's nice (although it suggests you don't visit many web sites) but sort of orthogonal to this HN topic you created. This tool Xt_sslpin doesn't do anything for TLS 1.3. It's a tiger-repelling rock. Maybe you don't see any tigers, but that's not because of the rock.
- deleted 5y ago[deleted]