<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SMTPS on DevLogs</title><link>https://blog.param.sh/tags/smtps/</link><description>Recent content in SMTPS on DevLogs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 02 May 2026 07:07:33 +0530</lastBuildDate><atom:link href="https://blog.param.sh/tags/smtps/index.xml" rel="self" type="application/rss+xml"/><item><title>CSR Formats, X.509 Standard, and more...</title><link>https://blog.param.sh/posts/other-components-of-tls/</link><pubDate>Sat, 02 May 2026 07:07:33 +0530</pubDate><guid>https://blog.param.sh/posts/other-components-of-tls/</guid><description>&lt;h1 id="what-are-x509-certificates"&gt;
 What are X.509 certificates?
 &lt;a class="heading-link" href="#what-are-x509-certificates"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;A X.509 is the standard certificate format of signed certificate which contains details like the server’s public key, the domain name it’s valid for, who issued it, how long it’s valid etc.&lt;/p&gt;
&lt;p&gt;You don’t really need to memorize the structure, but the idea is that every certificate on the internet follows the same blueprint, so browsers know exactly where to look for things like the public key, issuer, and signature. It’s what makes the whole system interoperable.&lt;/p&gt;</description></item></channel></rss>