Description of problem: Version-Release number of selected component (if applicable): vsftpd-1.2.1-3E.6 This bug seems to exists on centos 4.3 too. http://bugs.centos.org/view.php?id=1393 How reproducible: If i set user_config_dir in vsftpd.conf each user has to have a config file othervise the connection get's terminated. This behaviour is definitly wrong and the error message is misleading. The reason for this behaviour is a bug in file 'twoprocess.c' around line 422 see additional information. Additional info: /* Security - ignore unless owned by root */ if (!vsf_sysutil_retval_is_error(retval) && vsf_sysutil_statbuf_get_uid(p_statbuf) == VSFTP_ROOT_UID) { vsf_parseconf_load_file(str_getbuf(&filename_str), 1); } else { die('error reading non-root config file'); } THE BUG: The 'else' part (which throws the error) is not only entered if the config file is not owned by root, it is also entered if the user config file does not exist.
Hi there ! any news ?
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Notice: Just to remind the bug exists in the centos 4 package too. (see the centos bug report above).
Hi, please try vsftpd-1.2.1-3E.9.
from where do I get the package ?
i can test this package if you give me a download link :) I would be happy to know what changes has been made too ^^
Hi, sorry for delay, here is the link: http://people.redhat.com/rbiba/maros/vsftpd-1.2.1-3E.9.src.rpm
Thank you : Seems ok for the moment. I suggest to wait 24h for eventual side effect.
Ah, as the problem also exists on centos 4, do you plan to build a RPM for this release too ?
Red Hat doesn't support CentOS at all. If you are asking about this bug on rhel 4 I hope that soon.
Yes sorry, I spoke about rhel4. If you need I can open the same bug report for rhel 4 (to keep in mind).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0425.html
Thank you. Is it fixed for RHEL4 too ?