Bad owner or permissions on ~/.ssh/config even if [automount]options = "metadata"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Describe the solution you'd like
-
I want to sync ~/.ssh or some folder in windows and wsl
-
I found ssh would get error because of bad permissions
-
add
[automount] options = "metadata"to
/etc/wsl.confand chmod solve this temporarily . -
But after I alter
~/.ssh/configin by sublime in windows , the permissions changed -
get
Bad owner or permissionsagain in wsl -
Why it can't keep the fake permissions in wsl ?
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
Reproduce the sequence using /etc/wsl.conf with [automount] options = "metadata", then edit ~/.ssh/config in Windows with Sublime and check the resulting permissions in WSL. Determine why the metadata or fake permissions do not persist; done means the synchronized SSH configuration remains usable by ssh after Windows edits.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100