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
<Class> section is allowed to be in <Global>, but From directive is not #1597
Comments
Indeed, it looks like the |
…tion that is itself within a `<Global>` section. The underlying cause was the lack of creating a "Class" config context on the parser stack for the entire `<Class>` section. Without this, the `From` directives were not being associated into the `CONF_CLASS` configuration context, which in turn meant that the directive handler checks for proper context were failing unexpectedly.
…tion that is itself within a `<Global>` section. The underlying cause was the lack of creating a "Class" config context on the parser stack for the entire `<Class>` section. Without this, the `From` directives were not being associated into the `CONF_CLASS` configuration context, which in turn meant that the directive handler checks for proper context were failing unexpectedly.
…tion that is itself within a `<Global>` section. The underlying cause was the lack of creating a "Class" config context on the parser stack for the entire `<Class>` section. Without this, the `From` directives were not being associated into the `CONF_CLASS` configuration context, which in turn meant that the directive handler checks for proper context were failing unexpectedly.
Issue #1597: Properly handle `From` directives inside a `<Class>` sec…
The fix has been merged to the master branch, and backported to the 1.3.8 branch. Thanks! |
Thank you very much, I rebuilt proftpd in my dev environment and now it works as expected! Any idea when you are likely to release 1.3.8a with the various fixes you've backported? |
What I Did
I added a Class in my global config so that it could be used by both to root server config (FTP) and my virtualhost (SFTP). Ex:
Upon restarting proftpd, I got the following error message:
What I Expected/Wanted
I expected to restart Proftpd and have it work.
ProFTPD Version and Configuration
Please help us reproduce the problem/issue you are encountering. To do this,
we need to know which version of ProFTPD you are using, how it was built,
etc. The following command is an easy way to get all of this information:
In addition, we need to see all of the ProFTPD configuration files you are
using (minus any sensitive information like passwords, of course). Armed
with the version and configuration data, then, we can set up ProFTPD locally
using the same configuration, and see what happens.
proftpd.conf:
The text was updated successfully, but these errors were encountered: