docs(ssh): SSH-first setup path as a peer of the token path #348
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!348
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-299-ssh-first-setup-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The setup guide gains an SSH-first section of equal standing with the token path: choosing a protocol mode at login (https / ssh / ssh-only), what the SSH preflight checks (usable key, known_hosts TOFU fingerprint steer, identity probe), and what works token-less versus what degrades. The ssh-only degradation is documented with the verbatim typed error text, the pure-git vs API-dependent split is stated plainly, and the security rationale is given with its counterweights (TOFU is the weak point; madtea guards token storage but cannot guard a passphrase-less key file). COMPARISON/COMPAT were reasoned as already-covered. A --token passed in ssh-only is documented as ignored, not rejected.
Closes #299.
Closes #299