<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Authentication on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/authentication/</link>
		<description>Recent content in Authentication on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/authentication/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Auto-Approve Dead-End: A BBS Onboarding Bug Story</title>
				<link>https://phosphorbbs.net/blog/the-auto-approve-dead-end/</link>
				<pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/the-auto-approve-dead-end/</guid>
				<description>&lt;p&gt;Here&amp;rsquo;s a bug that&amp;rsquo;s easy to introduce and embarrassing to discover: a new user creates an account on your BBS, the system auto-approves them, generates a temporary password, and sends it to their BBS mailbox. The user can now read that password — by logging in. Which requires the password. Which is in the mailbox. Which they can&amp;rsquo;t open.&lt;/p&gt;&#xA;&lt;p&gt;Classic chicken-and-egg. Let me walk through how this happened, why it was hard to spot, and how we fixed it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
