Re:Why HTTPS for Everything?
by ycmbntrthrwaway on Monday January 02, 2017 @09:58AM
(#13301436)
Telnet/netcat seems simple only because all the layers below are hidden inside the operating system. You don't type in all the MAC/LLC/TCP headers, and you can avoid typing in TLS headers just by hiding them inside the library (LibreSSL, GnuTLS etc.). With libtls API you can think about cryptography in terms of "padlock icon" until you want to learn more.
[ Parent
| on HN ]
No, but you can build your own stack from scratch fairly easily, and it's easier to debug when you can see the plaintext through the data structures.
And it's easier to debug a video codec if it's ASCII art, but there's huge benefits for using TLS everywhere instead of plaintext, and they more than outweigh "it's harder to debug."
Re:Why HTTPS for Everything?
by paulddraper on Monday January 02, 2017 @11:00AM
(#13301829)
True, though reimplementing those is child's play compared to TLS.
Having done semi-serious implementations of both, I disagree. Implementing IP and TCP and getting it hooked up to your OS so that your packets get spat out the network card and your responses get relayed back to your code is much harder than implementing a minimal TLS.
Re:Why HTTPS for Everything?
by ycmbntrthrwaway on Monday January 02, 2017 @12:06PM
(#13302426)
True. Minimal TCP with 1 MSS window may be easy, but proper congestion control with fast recovery, F-RTO, tail loss probe, SACK etc. is much harder. Miss one of these aspects and you get a TCP that takes minutes to recover from a lost packet in some obscure case. It took years to debug Linux TCP stack. Even BSD stack is already way behind.
Re:Why HTTPS for Everything?
by paulddraper on Monday January 02, 2017 @12:15PM
(#13302522)
Given that the context is "ability to type commands to a web server over telnet as a learning experience", I was of course talking about minimal implementations. TCP with congestion control is hard, just as TLS with proper compatibility is hard.