4 ms·
Encrypted layers already exist in the current stack: MACsec for Ethernet or WPA et al for Wireless or 3G/4G since day one and so on for each option in the netwo
by zamadatix 5y ago
Encrypted layers already exist in the current stack: MACsec for Ethernet or WPA et al for Wireless or 3G/4G since day one and so on for each option in the network/interface layer, IPsec for the network layer, TLS for transport layer, and after that you're in the application layer which can choose it's encryption.
The friction with getting the lower layers encrypted hasn't been lack of option to do so in the current stack it's convincing everyone to throw out their middlebox setups to allow the encrypted protocols universally. Well that and encryption is more expensive (both performance and implementation cost) so the less you can get away with the easier it is to convince people to do. If that were easy to get people to change the middleboxes then we wouldn't be in this situation in the first place.
This is one of the main reasons why everything is over HTTPS these days: it was the lowest layer universally deployed net new protocol that was encrypted from day 1 and didn't have to worry about ossification as much. It's far easier to just use that as the new base transport layer and ignore the problem, doing so with new encrypted protocols over UDP when the functionality you're trying to replace in your protocol is at the TCP level.