cmderdev / cmderdev/cmder

Question: How do I change the route cmder has to find ssh keys?

Open
#2,930 25 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

❔ Type: Question 👆 Git
Dominant language
PowerShell
Stars
27k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Description

Question

Right now it searches in "~/.ssh "but i would like to put a relative path to not have to copy my keys in the home directory of every computer that I use instead of geting them from the external drive.
I have searched everywhere, I tried looking at user_profile.cmd, start-ssh-agent.cmd and init.bat.

Checklist
  • I have read the documentation and made sure what I'm looking for isn't present, or is unclear.
  • I have searched for similar issues, and either this question wasn't asked before, or I didn't find any that describe my question.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review user_profile.cmd, start-ssh-agent.cmd, and init.bat to trace where ~/.ssh is configured. Clarify whether Cmder supports a relative SSH-key path, then document the supported configuration and how to verify it.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.