Repository navigation
docs(f3): a fresh recovery sheet is a credential, so it costs the password - #106
Merged
Merged
Conversation
…sword Regeneration was the one credential mutation on the settings screen that asked only a confirmation. A confirmation is a question for the reader who meant it; it is no obstacle to whoever is holding the session, who simply answers it. What comes out is a bearer credential that outlives the session that minted it. F3-R35 ends every other session on a password change and does not retire a sheet, so an unlocked session left open bought entry the account holder could not revoke. F3-R39 puts the account password in front of it, which is the proof in-app deletion already takes on the same screen. The command-line path keeps its exemption: F3-R14 already says access to the machine is its proof. Spec: F3-R39 Signed-off-by: Wessel Verheij <info@nightworks.io>
|
lessevv
enabled auto-merge (squash)
September 13, 2026 09:00
github-actions
Bot
added
the
awaiting-maintainer
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regeneration was the one credential mutation on the settings screen that asked only a confirmation. A confirmation is a question for the reader who meant it; it is no obstacle to whoever is holding the session, who simply answers it.
What comes out is a bearer credential that outlives the session that minted it.
F3-R35ends every other session on a password change and does not retire a sheet, so an unlocked session left open bought entry the account holder could not revoke.F3-R39puts the account password in front of it — the proof in-app account deletion already takes two cards further down the same screen. The command-line path keeps its exemption:F3-R14already says access to the machine is its proof.The implementation PR in
beatraxcites this id and follows.Spec: F3-R39