Authentication Is a Chain of Fallbacks
Security keys can reduce routine password exposure, but adding a key does not erase passwords, recovery media, cached sessions, or other authentication paths.
Goal
Identify how a system’s primary authenticator, fallback credentials, recovery assets, and privilege boundaries work together.
Activity
Give students this fictional setup:
A Linux laptop uses a FIDO2 key and PIN to unlock its encrypted disk, log in, authorize sudo, and connect by SSH. The original disk passphrase and account password remain available for recovery.
Students create a four-row table for disk unlock, desktop login, sudo, and SSH. For each path, record:
- the normal authenticator;
- the remaining fallback;
- what must be backed up or retained;
- one lockout risk;
- one observable test of success;
- how access would be revoked after a lost key.
Then students answer: “Does adding a security key make this system passwordless?” Support the answer with two details from the table.
Deliverable
Submit the completed authentication-path table and a 150-word recommendation identifying which path should be tested first and why.
Discussion and safety
This is a paper-design exercise. Do not alter authentication, encryption, PAM, SSH, or disk settings on a production computer. Use a fictional system and redact all real account names, addresses, fingerprints, and recovery information.
Source material
First spotted in the November 22, 2026 PTIR Daily Briefing. The Fedora Linux 45 FIDO2 lab carefully separates encrypted-disk enrollment, PAM registration, privilege elevation, and SSH, while retaining recovery credentials and reporting unsuccessful hardware tests. It generated this activity because the guide makes authentication visible as a chain of distinct controls rather than a single login screen.