You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is still a bug. The behavior of .. bouncing off the root is well-known and stuff depends on this working.
In order to test this on unix systems, currently ChrootDirectory %h on unix systems currently requires the home directory
to be owned by root and not writable by anybody else, so this needs to be tested with a writable subdirectory:
# chown root ~test
# chown chmod 755 ~test
# mkdir ~test/sub
# chown test~test/sub
# sftp loalhostsftp>ln -s ../.. sub/grandparentsftp>ls sub/grandparent(lists /home/test but on Windows lists C:\Users)
Additional test cases (to avoid breaking something else)
sftp>ln -s root /sftp>ls root(should list C:\Users\test and does)
sftp>mkdir aaasftp>ln -s ../Documents aaa/docssftp>ls aaa/docs(should list C:\Users\test\Documents and does)
The text was updated successfully, but these errors were encountered:
Prerequisites
Steps to reproduce
Create test user account
Turn on Developer Mode
Load into sshd_config:
(In fact any writable directory will do, or even a writable subdirectory, but with different steps to reproduce)
Log in with sftp
Run the following commands
Expected behavior
shows listing of c:\users\test
Actual behavior
shows listing of c:\users
Error details
No error message generated
Environment data
Not applicable; powershell itself is not in the reproduction steps
Version
OpenSSH_for_Windows_9.8p1 Win32-OpenSSH-GitHub, LibreSSL 3.9.2
Additional Info
MSRC Case 91638 reports: Not a vulnerability
This is still a bug. The behavior of .. bouncing off the root is well-known and stuff depends on this working.
In order to test this on unix systems, currently ChrootDirectory %h on unix systems currently requires the home directory
to be owned by root and not writable by anybody else, so this needs to be tested with a writable subdirectory:
Additional test cases (to avoid breaking something else)
The text was updated successfully, but these errors were encountered: