<?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[Topics tagged with dagger]]></title><description><![CDATA[A list of topics that have been tagged with dagger]]></description><link>https://board.circlewithadot.net/tags/dagger</link><generator>RSS for Node</generator><lastBuildDate>Sat, 30 May 2026 15:10:50 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/dagger.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[My migration from GitHub to Gitea became stalled when I realized that you can tie self-hosted Actions runners to]]></title><description><![CDATA[https://github.com/Infisical/agent-vaultThis looks fascinating. An open-source credential broker by Infisical that sits between your agents and the APIs they call.Agents should not possess credentials. Agent Vault eliminates credential exfiltration risk with brokered access.And that can be self-hosted or operated as SaaS. Going to follow this up next week, looking to see if this scales for larger dev teams. The best defense against supply-chain compromise is being able to manage credentials. For many new AI threats, that will be the same. #agentic #saas #agaas #credentialtheft]]></description><link>https://board.circlewithadot.net/topic/9672688d-3cd8-4c9a-86c2-ae3fa6a1e9a3/my-migration-from-github-to-gitea-became-stalled-when-i-realized-that-you-can-tie-self-hosted-actions-runners-to</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/9672688d-3cd8-4c9a-86c2-ae3fa6a1e9a3/my-migration-from-github-to-gitea-became-stalled-when-i-realized-that-you-can-tie-self-hosted-actions-runners-to</guid><dc:creator><![CDATA[windsheep@infosec.exchange]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>