proftpd package is missing from epel 8 repository. How could I know if there's some work in progress on it or if it's permanently dropped? Thank you.
I was considering whether or not I should wait for 1.3.7 to be released. I try not to do version updates in EPEL for stability reasons. Changes of note that will be in 1.3.7: https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES Project milestone is at 85% at the moment: https://github.com/proftpd/proftpd/milestone/1 I don't think 1.3.7 will be released any time soon really, so I'm inclined to stick with 1.3.6. I do want to use the split configuration that's in the current rawhide version, and it'd be good to get some feedback on whether there are any issues in respect of that.
Thank you for the informations. Unfortunately I'm using older versions of proftpd so I don't have much to contribute to your considerations. Maybe a little OT, but: are there any official channels (besides opening bugs) to be updated about package release status in EPEL? (I have similar issues with gdal, also missing)
(In reply to Daniele Branchini from comment #2) > Thank you for the informations. > > Unfortunately I'm using older versions of proftpd so I don't have much to > contribute to your considerations. Here's a scratch build you might like to try. It'll be around for a couple of weeks probably before it gets auto-deleted: https://koji.fedoraproject.org/koji/taskinfo?taskID=38125592 > Maybe a little OT, but: are there any official channels (besides opening > bugs) to be updated about package release status in EPEL? (I have similar > issues with gdal, also missing) It's basically down to the packagers, so raising bugs is the way to go really. Some packagers have to deal with lots of packages, so they build the ones they're specifically asked for, at least at first. For repository-wide issues that span multiple packages, the EPEL development list would be the best place to go: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/
(In reply to Paul Howarth from comment #3) Thank you very very much for your thorough answer. I'm going to try the scratch build in the next few days.
I'd also like to see ProFTPd in EPEL 8. Temporarily we rebuilt 1.3.5 from EPEL 7 (with all of its dependencies), but this is not sustainable long term. Their numbering scheme is a bit confusing, but CVE-2019-12815 is another reason to ask for a possible release to EPEL 8 of a recent (even if an rc?) version.
(In reply to Assen Totin from comment #5) > I'd also like to see ProFTPd in EPEL 8. Temporarily we rebuilt 1.3.5 from > EPEL 7 (with all of its dependencies), but this is not sustainable long > term. Their numbering scheme is a bit confusing, but CVE-2019-12815 is > another reason to ask for a possible release to EPEL 8 of a recent (even if > an rc?) version. Your rebuild of 1.3.5 from EPEL-7 should not be vulnerable to CVE-2019-12815: https://bugzilla.redhat.com/show_bug.cgi?id=1732367 There isn't a release candidate for 1.3.7 yet. How about I build the package as per the scratch build in Comment #3 in epel8-playground for now (see https://lwn.net/Articles/796202/) and we'll see if there are any issues with the packaging. If all is well after a while, I'll do the same build in epel8 proper and when the 1.3.7 release candidates come out, I'd do those in epel-8 playground?
ProFTPd 1.3.6a is now available in epel-playground. Please give it a try and comment here if you do. If feedback after a month or so is good, I'll build it in epel8 proper and will then put 1.3.7rc1 in epel8-playground.
(In reply to Paul Howarth from comment #7) > ProFTPd 1.3.6a is now available in epel-playground. Please give it a try and > comment here if you do. We've been trying the epel-playground build, so far so good (we're comparing transfer between different proftpd servers) The only thing that we're still investigating (and might be completely unrelated to the ProFTPd package itself) is slowness on sftp logins compared to a similar configured ProFTPd 1.3.5a on CentOS7: there is a noticeable delay (about 6 seconds) in logins (even with `mod_delay` turned off).
ProFTPd 1.3.6b is now available in epel-playground but I wouldn't expect it to make any difference to the login delays. It would probably be best to ask upstream about that.
I've updated to the 1.3.6b, thank you. For the record, the login delays were due to a network issue unrelated to ProFTPd or its packaging.
Thanks, that's good to know.
Hi Paul, thank you for your build. I have installed proftpd from the playground repo and it's working fine. I would love to see it in epel8 production repo :-)
I am not sure 100%, but there may be problem with SQL or MySQL modules. In my new config(CentOS8.1+ProFTPd v 1.3.6b from epel-playground) I cannot login to ftp-server due problems with authorisation (user accounts stored in MySQL DB). What`s interesting, in SQL-logs no trace of attempts to connect from ftp-server. :( P.S. Other services correctly working with MySQL-server. P.P.S. According to proftpd -vv, mod_sql_mysql/4.0.9 & mod_sql/4.3 successfully loaded. And proftpd configs seems correct (at least they worked on CentOS7). I have no idea how to trace work of proftpd-MySQL module with MySQL at this moment.
(In reply to Alexander Dyadyun from comment #13) > I am not sure 100%, but there may be problem with SQL or MySQL modules. > In my new config(CentOS8.1+ProFTPd v 1.3.6b from epel-playground) I cannot > login to ftp-server due problems with authorisation (user accounts stored in > MySQL DB). > What`s interesting, in SQL-logs no trace of attempts to connect from > ftp-server. :( > > P.S. Other services correctly working with MySQL-server. > > P.P.S. According to proftpd -vv, mod_sql_mysql/4.0.9 & mod_sql/4.3 > successfully loaded. And proftpd configs seems correct (at least they worked > on CentOS7). I have no idea how to trace work of proftpd-MySQL module with > MySQL at this moment. SELinux perhaps? Is the ftpd_connect_db boolean set? Other possibility could be firewall.
(In reply to Paul Howarth from comment #14) > > SELinux perhaps? > > Is the ftpd_connect_db boolean set? > > Other possibility could be firewall. No, there something more tricky :) SELinux is completely off. Firewall on SQL-server allow any sql-connects from local network (other servers from local network works perfectly). I tried to set SQLLogFile, but without success - no info appears in file. <IfModule mod_sql.c> SQLLogFile /var/log/proftpd/sql.log ..... </IfModule> in debug.log (proftpd -nd10 2>&1 >& /var/log/proftpd/debug.log): dispatching PRE_CMD command 'PASS (hidden)' to mod_tls dispatching PRE_CMD command 'PASS (hidden)' to mod_core dispatching PRE_CMD command 'PASS (hidden)' to mod_core dispatching PRE_CMD command 'PASS (hidden)' to mod_vroot dispatching PRE_CMD command 'PASS (hidden)' to mod_sql dispatching PRE_CMD command 'PASS (hidden)' to mod_delay dispatching PRE_CMD command 'PASS (hidden)' to mod_auth dispatching CMD command 'PASS (hidden)' to mod_auth USER Shurik: no such user found from 192.168.1.99 [192.168.1.99] to ::ffff:192.168.1.21:21 dispatching POST_CMD_ERR command 'PASS (hidden)' to mod_sql dispatching POST_CMD_ERR command 'PASS (hidden)' to mod_vroot dispatching POST_CMD_ERR command 'PASS (hidden)' to mod_delay dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_sql dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_log dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_delay dispatching LOG_CMD_ERR command 'PASS (hidden)' to mod_auth dispatching PRE_CMD command 'QUIT' to mod_tls dispatching PRE_CMD command 'QUIT' to mod_core dispatching PRE_CMD command 'QUIT' to mod_core dispatching CMD command 'QUIT' to mod_core dispatching POST_CMD command 'QUIT' to mod_sql dispatching LOG_CMD command 'QUIT' to mod_sql dispatching LOG_CMD command 'QUIT' to mod_log dispatching LOG_CMD command 'QUIT' to mod_core FTP session closed.
Probably best asking upstream I think.
Sorry for false alarm! ProFTPd works perfectly, but my brains not :) Childish error with file paths in my new config.
I did a build for proftpd in epel8, which should turn up in epel-8-testing soon: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-971c9b92bd Once that goes to epel8 stable, I'll take a look at the current release candidate for 1.3.7 for epel8-playground. Feel free to remind me in case I forget...
proftpd-1.3.6b-3.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-971c9b92bd
proftpd-1.3.6b-3.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.
As promised, proftpd 1.3.7rc3 has now been built for epel8-playground. It should turn up in the repo soon.