mysql / mysql/mysql-shell-plugins
Support SSH-agent authentication for MySQL Workbench connections
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 96
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
MySQL Workbench connection settings currently require a private key file for SSH tunnels. Add an SSH Agent authentication option so MySQL Shell can use identities exposed by the platform agent, including hardware-backed YubiKey identities.\n\nA tested implementation and regression tests are available in a contributor fork: https://github.com/Phreak420/mysql-shell-plugins/tree/feature/windows-ssh-agent-auth\n\nOn Windows with Kleopatra/Gpg4win, the bundled libssh transport also needs native support for the standard \\\\\.\\pipe\\openssh-ssh-agent\\ named pipe; that transport change is being prepared separately for libssh upstream.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the tested implementation and regression tests in the contributor fork, then inspect the MySQL Workbench connection settings and the Windows libssh transport requirement described here. Done means SSH-agent authentication works with platform and hardware-backed identities, with regression coverage and the required Windows named-pipe support addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, typescript
- Domain
- authentication, desktop, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100