mirror of
https://github.com/ergosteur/ssh-protocol-handler-win.git
synced 2026-10-28 08:10:35 -04:00
1bd676d2fecc93616485d770bb97f03a19ed2f71
The direct HKCR\ssh\shell\open\command write (what SshHandler and the initial Rust port both did) doesn't actually get honored once a UserChoice already exists for the ssh scheme, which is the normal state on Windows 10/11 — so registration silently no-ops from the user's perspective. Switch to the same "Default Programs" capability registration openssh_protocol_handler.bat uses: a dedicated ProgID with Capabilities\UrlAssociations plus a HKLM\SOFTWARE\RegisteredApplications entry, so the app actually shows up in and can be selected from Settings > Apps > Default Apps > "Choose default apps by link type". Uses its own identifier, ssh_handler_rs, distinct from the batch script's ssh_custom_handler so the two don't collide. Verified end-to-end under Wine: registry keys land exactly as expected (checked via `wine reg query`), and both the setup and connect dialogs still render correctly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GYCT2RpUjFfBfp6CD4rREw
ssh-protocol-handler-win
ssh protocol handler for Windows using Windows' built-in OpenSSH
Languages
Shell
42.1%
Rust
37%
Batchfile
20.5%
C
0.4%