Prompt when key has changed?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- security
Research direction
Start by tracing the Posh-SSH connection path and its registry-based cached-key handling, then compare the related behavior in the rencli ssh project mentioned in the report. Clarify the expected prompt and acceptance behavior for a key mismatch, including how an accepted replacement key is stored; the issue is complete when this behavior is defined and covered for affected connections.
Written by the indexing model from the issue text.
Description
Thank you for all of your work on this module - it certainly makes my teams job much easier and is much appreciated!
We ran into an issue this week - as we manage a network on 700 routers and switches and we use powershell and this module for our automation. We were having an issue connecting to a handful of devices - getting the error message "key exchange negotiation failed". We have dns entries for all of our routers. The confusing part was, when I connect to the IP, it would error. DNS name would succeed.
After some debugging in this and the rencli ssh project I found that this was due to the key not matching the cached key in the registry. Turns out that our field team had replaced these problem devices.
Would it be possible (or even a good idea) to prompt that the key does not match and ask to accept??
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from darkoperator/Posh-SSH
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
darkoperator/Posh-SSH#626 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
darkoperator/Posh-SSH#625 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
darkoperator/Posh-SSH#623 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
darkoperator/Posh-SSH#621 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
darkoperator/Posh-SSH#617 · 2 comments ·
All issues in darkoperator/Posh-SSH
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sisaku-security/sisakulint#647 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yunaremaia/driftcheck#246 ·
-
Docs say approvals.mode defaults to smart, but code falls back to manual when the key is absent Openarea/config comp/tools P2 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#117341 · 1 comment ·
-
bug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yunaremaia/taintrace#110 ·