Skip to content

ssh: verify hints match the flow that ran (manual vs 1Password) - #59

Open
keithharvey wants to merge 1 commit into
beyond-all-reason:masterfrom
keithharvey:ssh-verify-flavor
Open

ssh: verify hints match the flow that ran (manual vs 1Password)#59
keithharvey wants to merge 1 commit into
beyond-all-reason:masterfrom
keithharvey:ssh-verify-flavor

Conversation

@keithharvey

Copy link
Copy Markdown
Contributor

op_ssh_verify is shared by the 1Password and manual SSH setup flows, but its remediation text was hardwired to the 1Password story — a just ssh::manual-setup user whose key GitHub rejects gets told to check what 1Password is exposing.

  • op_ssh_verify takes a flavor arg (op default, manual); each failure branch (no agent / no keys / GitHub denied) now gives flow-appropriate hints
  • manual flavor's denied hint flags the common trap: key added as a Signing Key instead of an Authentication Key, or on the wrong account
  • ${SSH_AUTH_SOCK:-unset} so the no-agent branch can't trip set -u

🤖 Generated with Claude Code

op_ssh_verify's remediation text was hardwired to the 1Password story,
so a manual-setup failure told users to check 1Password. Flavor arg
picks the hints; manual flow also flags the Signing-Key-vs-Auth-Key trap.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@thvl3 thvl3 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need a 1password flow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants