-
Notifications
You must be signed in to change notification settings - Fork 468
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
linux_env - FileSystem::resolve_path and FileSystem::readlink seems incompatible #1116
Comments
Hi, It might not be the best solution, but the way I saw it, the filesystem should be relative to the sandbox root. Ie, it should work the same way than a chroot, so the link should point to The current implementation might be buggy, but what do you think about this way of doing? |
Hi, Right now, with symbolic which point to
It could be nice. I have one question about it : What happens if the link is valid? I think it's still good, are you agree? What do you think about getting target of symbolic link only if
|
Hi, I'm not sure to understand the step description, but we're maybe saying the same thing. IMHO, we want two things:
So, if the |
My architecture:
FileSystem::resolve_path
reads link and breaksFileSystem::readlink
function because of wrong return value. See below:The text was updated successfully, but these errors were encountered: