Can't access files in a folder accessed through a symbolic link if link created with `/` affixed.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 6.4k
- Forks
- 315
- PR merge metrics
- No merged PRs in 30d
Description
This one took me down a rabbit hole, but I was victorious!
I had an older Debian machine where I could access and create files inside a folder accessed through a symbolic link and another one where same folder with same files and permissions didn't work.
Long story short the culprit was / as part of my symbolic link, so when creating a symlink to folder specify the target as /foo/bar instead of /foo/bar/.
lrwxrwxrwx 1 root root 26 Oct 23 00:14 freeswitch-will-work -> /usr/local/freeswitch/conf
lrwxrwxrwx 1 root root 27 Oct 23 00:20 freeswitch-not-working -> /usr/local/freeswitch/conf/
For completeness, this is on Debian 9, with OpenSSH 7.4
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.
Research direction
The report names no source file, test, or entry point. Start by reproducing the behavior on Debian 9 with OpenSSH 7.4 using symlink targets with and without a trailing slash. Done means the behavior is explained or fixed and the differing cases are covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100