<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Drylm - Thoughts from the void. (Posts about ssl)</title><link>https://blog.drylm.org/</link><description></description><atom:link href="https://blog.drylm.org/categories/ssl.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 28 Dec 2025 14:59:07 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Microsoft SSL implementation usage is a mess(l)</title><link>https://blog.drylm.org/posts/microsoft-ssl/</link><dc:creator>Jonathan Muller</dc:creator><description>&lt;div&gt;&lt;h3&gt;TLS/SSL Description&lt;/h3&gt;
&lt;p&gt;Since the different applicative protocols can run with or without SSL, servers must expose dedicated port (443 for https) or switch (STARTTLS in SMTP, POP, NNTP)&lt;/p&gt;
&lt;p&gt;Above a description of the handshake between a client and a server running TLS (or SSL)&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.drylm.org/posts/microsoft-ssl/"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>.net</category><category>c&amp;#35;</category><category>microsoft</category><category>network security</category><category>ssl</category><category>tls</category><guid>https://blog.drylm.org/posts/microsoft-ssl/</guid><pubDate>Thu, 15 Jan 2015 00:00:00 GMT</pubDate></item></channel></rss>