Skip to content

mod_vroot changes interpretation of <Directory> paths #1

@Castaglia

Description

@Castaglia

Assume you have the following in your proftpd.conf:

DefaultRoot ~
VRootEngine on

<Directory /full/path/to/dir>
  ...
</Directory>

With this configuration, the <Directory> configuration directives will never be applied. This happens because of how mod_vroot changes the handling/construction of paths within the core proftpd engine.

Currently, with this configuration, the workaround would be to change the <Directory> path to not be the absolute path, but instead be relative to the chrooted path. That is, for the above config, if the DefaultRoot ~ caused the user to be chrooted to /full/path, then for the <Directory> section to work, it would have to look like:

<Directory /to/dir>
  ...
</Directory>

which is non-obvious (and does not work across multiple varied DefaultRoot directories).

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions