-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
symlinked items don't preserve file permissions #92
Comments
I've experienced this issue as well. I have my |
Well, yeah. :-)
Airquotes indeed. So far you haven't reported any bugs :-) |
Some CLI tools don't see it that way, for example the ssh key agent on linux distros (like Ubuntu and Fedora). Because of the symlink's 777 permissions the agent ignores the key |
This sounds like a similar issue I had with the ssh config. It ended up being an issue with git and not homeshick. See if something like this would fix your key issues: #93 (comment) |
That's just not true. I tried it out 5 minutes ago (on debian, which runs the same openssh every other distro does), something else must be wrong on your setup (maybe your p.s.: If this really were the case, enforcing the permissions would make no sense at all. They are enforced to make sure that nobody but you can change the contents of e.g. the |
The file that get symlinked from a castle don't preserve their file permissions (for example one of my file had "600" but it got turned into "777")
ps: sorry for creating so many issues in such a short time but I'm really loving the idea behind homeshick and I just can't enjoy it enough while these "bugs" exist.
The text was updated successfully, but these errors were encountered: