<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>trust &#8211; it.megocollector.com</title>
	<atom:link href="https://it.megocollector.com/tag/trust/feed/" rel="self" type="application/rss+xml" />
	<link>https://it.megocollector.com</link>
	<description>The information technology compendium</description>
	<lastBuildDate>Sun, 26 Jul 2026 01:26:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>TrustView: A Self-Hosted SSL Certificate Dashboard for Your Homelab</title>
		<link>https://it.megocollector.com/linux/trustview-a-self-hosted-ssl-certificate-dashboard-for-your-homelab/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 26 Jul 2026 13:18:41 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[cert]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[pki]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[trust]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=7171</guid>

					<description><![CDATA[Every homelabber and small-ops admin knows the moment: you browse to one of your own services and get slapped with a full-screen certificate warning. The cert expired three days ago. Nothing told you. Now you&#8217;re renewing it under pressure instead of on a schedule. I got tired of that moment, so I built TrustView — a lightweight, self-hosted dashboard that...]]></description>
		
		
		
			</item>
		<item>
		<title>Fix trust relationship between workstation and primary domain</title>
		<link>https://it.megocollector.com/windows/fix-trust-relationship-between-workstation-and-primary-domain/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 25 Jun 2024 19:39:10 +0000</pubDate>
				<category><![CDATA[Windows]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[trust]]></category>
		<category><![CDATA[workstation]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=6463</guid>

					<description><![CDATA[The following solution was tested on a Windows 10 Professional workstation joined to an Active Directory domain. When a domain-joined PC loses its secure channel with the domain controller, you&#8217;ll see this error at login. Rather than removing and re-joining the machine to the domain (the traditional fix), you can resolve it quickly using PowerShell — no reboot required. Step...]]></description>
		
		
		
			</item>
	</channel>
</rss>
