Bug Fixes
6- A relative copy such as scp server:file.txt . failed with No such file or directory, while the same copy written with the full path worked. The SFTP session opened at the root of the jail rather than in the account home, so a relative name was looked up one level above every file the account owns.
- Sessions now open in the account home for both SFTP-only and full SSH accounts. Relative scp, scp in legacy mode used by WinSCP, rsync and uploads all work; copies written with a full path keep working exactly as before.
- Accounts with a custom home directory are covered: the directory is mounted at the same point inside the jail, so the session lands in the right place.
- If the home directory is missing the session still opens at the jail root, so no account can be locked out by this change.
- The sshd rule for SFTP-only accounts is corrected when the panel starts, so no manual step is needed after updating.
- Resource limits, additional allowed directories and the shell restriction on SFTP-only accounts are unchanged.