<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mtls on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/mtls/</link><description>Recent content in Mtls on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 27 Aug 2026 06:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/mtls/index.xml" rel="self" type="application/rss+xml"/><item><title>mTLS for a desktop monitoring tool (and why you shouldn't use a cloud)</title><link>https://www.visorcraft.com/news/2026/08/mtls-for-a-desktop-monitoring-tool/</link><pubDate>Thu, 27 Aug 2026 06:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/08/mtls-for-a-desktop-monitoring-tool/</guid><description>&lt;p&gt;Somewhere in the last ten years, &amp;ldquo;I want to see the CPU graph on my other machine&amp;rdquo; quietly turned into a SaaS product with an agent, a relay server, an account, and a pricing page, and the whole arrangement is strange when you sit with it for a minute, because the two machines are yours, the data is a stream of numbers about hardware you own, and the only thing the cloud in the middle is actually contributing is a rendezvous point and a monthly invoice. LinSight&amp;rsquo;s answer to remote monitoring is that there is no middle: the daemon already serves everything over a Unix socket on the local machine, so the remote feature is a small binary called &lt;code&gt;linsight-tunnel&lt;/code&gt; that pipes those socket bytes over a mutually authenticated TLS connection to another &lt;code&gt;linsight-tunnel&lt;/code&gt; on your desktop, where it re-materializes as a local Unix socket that the GUI, the CLI, and the Prometheus scraper connect to as if the daemon were sitting right there.&lt;/p&gt;</description></item></channel></rss>