<story><title>Why HTTPS for Everything?</title><url>https://https.cio.gov/everything/</url></story><parent_chain><item><author>timthorn</author><text>I feel for later generations - learning tech gets harder and harder. Of course as the sum of knowledge increases this must be true, but as we go HTTPS-only the ability to type commands to a web server over telnet as a learning experience will be a loss.</text></item></parent_chain><comment><author>discreditable</author><text>&amp;gt; the ability to type commands to a web server over telnet as a learning experience will be a loss.&lt;p&gt;You can do this with openssl.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    openssl s_client -connect news.ycombinator.com:443
    GET &amp;#x2F; HTTP&amp;#x2F;1.1
    Host: news.ycombinator.com
&lt;/code&gt;&lt;/pre&gt;
Press enter twice and you&amp;#x27;ll get HTML.</text></comment>
<story><title>Why HTTPS for Everything?</title><url>https://https.cio.gov/everything/</url></story><parent_chain><item><author>timthorn</author><text>I feel for later generations - learning tech gets harder and harder. Of course as the sum of knowledge increases this must be true, but as we go HTTPS-only the ability to type commands to a web server over telnet as a learning experience will be a loss.</text></item></parent_chain><comment><author>ycmbntrthrwaway</author><text>Telnet&amp;#x2F;netcat seems simple only because all the layers below are hidden inside the operating system. You don&amp;#x27;t type in all the MAC&amp;#x2F;LLC&amp;#x2F;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 &amp;quot;padlock icon&amp;quot; until you want to learn more.</text></comment>