<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W?]]></title><description><![CDATA[<p>Lazyweb, a question: if (1) run a certificate authority let's call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W?</p><p>I mean "get the page at all", not "have a fallback option" or "see a warning". </p><p>I mean for people with A installed they it's a normal website and for people without A it's completely inaccessible.</p>]]></description><link>https://board.circlewithadot.net/topic/d6429bed-8730-49ac-9e8d-5bcc2708b27f/lazyweb-a-question-if-1-run-a-certificate-authority-let-s-call-a-and-a-web-server-w-is-there-a-way-for-me-to-say-that-a-client-c-must-have-a-manually-installed-as-trusted-ca-in-order-to-get-a-web-page-from-w</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 02:35:18 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/d6429bed-8730-49ac-9e8d-5bcc2708b27f.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 14 May 2026 21:30:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:56:52 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> it sounds like you’re looking for mutual authentication? <a href="https://en.wikipedia.org/wiki/Mutual_authentication" rel="nofollow noopener"><span>https://</span><span>en.wikipedia.org/wiki/Mutual_a</span><span>uthentication</span></a></p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/TindrasGrove/statuses/116575162348564483</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/TindrasGrove/statuses/116575162348564483</guid><dc:creator><![CDATA[tindrasgrove@infosec.exchange]]></dc:creator><pubDate>Thu, 14 May 2026 21:56:52 GMT</pubDate></item><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:53:06 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> yeah... nginx does not provide a variable with a server cert verification error, apache doesn't seem to have any similar tool as well.</p><p>Also thinking about this, if a client trusts the server cert directly without having the CA cert installed, it wouldn't send a TLS alert. The connection will just succeed.</p><p>If you're going to be installing a custom cert on the clients, you might as well make it a client cert. This has the benefit of using a tried and tested authentication method.</p>]]></description><link>https://board.circlewithadot.net/post/https://social.petko.me/users/petko/statuses/116575147524541471</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://social.petko.me/users/petko/statuses/116575147524541471</guid><dc:creator><![CDATA[petko@social.petko.me]]></dc:creator><pubDate>Thu, 14 May 2026 21:53:06 GMT</pubDate></item><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:40:02 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> closest thing I've ever seen is in Radius, where the Radius *server* gets a TLS Alert "bad certificate" whenever a client fails to connect to it due to a failure in the server cert validation.</p><p>Maybe TLS Alert is a good keyword to look into (<a href="http://www2.gnutls.org/manual/html_node/The-TLS-Alert-Protocol.html" rel="nofollow noopener"><span>http://</span><span>www2.gnutls.org/manual/html_no</span><span>de/The-TLS-Alert-Protocol.html</span></a>)</p>]]></description><link>https://board.circlewithadot.net/post/https://social.petko.me/users/petko/statuses/116575096190214988</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://social.petko.me/users/petko/statuses/116575096190214988</guid><dc:creator><![CDATA[petko@social.petko.me]]></dc:creator><pubDate>Thu, 14 May 2026 21:40:02 GMT</pubDate></item><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:37:07 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> You could get partway to what it seems like you want by having W require a _client_ certificate, signed by A, for any TLS connection, but then you have to provision client certs for each client - not just configure them to trust A.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.transneptune.net/users/owen/statuses/116575084717171768</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.transneptune.net/users/owen/statuses/116575084717171768</guid><dc:creator><![CDATA[owen@mastodon.transneptune.net]]></dc:creator><pubDate>Thu, 14 May 2026 21:37:07 GMT</pubDate></item><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:36:52 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> I suppose <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="nofollow noopener"><span>https://</span><span>developer.mozilla.org/en-US/do</span><span>cs/Web/HTTP/Reference/Headers/Strict-Transport-Security</span></a> will be a possible solution.</p>]]></description><link>https://board.circlewithadot.net/post/https://oslo.town/users/hallvors/statuses/116575083699786127</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://oslo.town/users/hallvors/statuses/116575083699786127</guid><dc:creator><![CDATA[hallvors@oslo.town]]></dc:creator><pubDate>Thu, 14 May 2026 21:36:52 GMT</pubDate></item><item><title><![CDATA[Reply to Lazyweb, a question: if (1) run a certificate authority let&#x27;s call A, and a web server W, is there a way for me to say that a client C must have A manually installed as trusted CA in order to get a web page from W? on Thu, 14 May 2026 21:34:45 GMT]]></title><description><![CDATA[<p><span><a href="/user/mhoye%40cosocial.ca">@<span>mhoye</span></a></span> _Specifically_ that the client must be manually configured to trust the issuer? Not in any commonly-deployed configuration I'm aware of, no. TLS implementations tend to make very little distinction between system, managed, and user-provided trust roots.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.transneptune.net/users/owen/statuses/116575075410971364</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.transneptune.net/users/owen/statuses/116575075410971364</guid><dc:creator><![CDATA[owen@mastodon.transneptune.net]]></dc:creator><pubDate>Thu, 14 May 2026 21:34:45 GMT</pubDate></item></channel></rss>