Bug 22566 - pure-ftpd no longer read the config /etc/pure-ftpd/pure-ftpd.conf
Summary: pure-ftpd no longer read the config /etc/pure-ftpd/pure-ftpd.conf
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Stig-Ørjan Smelror
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 22574
Blocks:
  Show dependency tree / graph
 
Reported: 2018-02-10 22:11 CET by Dieter Schütze
Modified: 2019-04-04 14:36 CEST (History)
3 users (show)

See Also:
Source RPM: pure-ftpd-1.0.47-1.1.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dieter Schütze 2018-02-10 22:11:16 CET 
Description of problem:

after upgrade from Mageia 5 to 6 pure-ftpd no longer use the config file in
/etc/pure-ftpd/pure-ftpd.conf

How reproducible:
on every changes

Steps to Reproduce:
1. edit conf file to use mysql with additional config in /etc/pure-ftpd/pureftpd-mysql.conf
pure-ftpd doesn#t read this and use mysql only pam is used
2. edit conf to use TLS ( TLS    1 )
pure-ftpd start up normal without tls
3. change the conf file to use specific ports ( PassivePortRange   60000 60999 )
pure-ftpd use only the standard ports

a direct start over /usr/sbin/pure-ftpd /etc/pure-ftpd/pure-ftpd.conf doesn't help.
I saw that the perl script /usr/sbin/pure-conf.pl from Mageia5 doesn't exist anymore.
is this not needed anymore ?
I don't think that pure-ftpd understand the conf file directly.
I think it must be translated from entries like
PassivePortRange   60000 60999  to -p60000:60999

Regards
Dieter
Stig-Ørjan Smelror 2018-02-10 23:12:10 CET

Assignee: bugsquad => smelror
CC: (none) => smelror

Comment 1 Stig-Ørjan Smelror 2018-02-11 00:05:20 CET 
Hi.

I've not been able to reproduce your issues using the same version as you.

I changed the Bind variable, set the port to 2100 and was able to log in.

Enabled mysql auth, disabled PAM auth and was unable to log in since I didn't set up the DB.

Enabled TLS, but pure-ftpd failed to start because of missing certificates.

I started pure-ftpd as such:
sudo /usr/sbin/pure-ftpd /etc/pure-ftpd/pure-ftpd.conf

Anyway, I will try to see if there is anything that can be improved.

Cheers,
Stig
Comment 2 Dieter Schütze 2018-02-11 00:22:17 CET 
Additional Info

after openssl dhparam -out /etc/ssl/private/pure-ftpd-dhparams.pem 2048
additional to the certificates that i use, i can start with

/usr/sbin/pure-ftpd /etc/pure-ftpd/pure-ftpd.conf

but i can't start with 
systemctl start pure-ftpd
or
/etc/init.d/pure-ftpd start

after i have change the line in /etc/init.d/pure-ftpd 
from

daemon $pure_launch_script $pure_config --daemonize
to
$pure_launch_script $pure_config

after systemctl daemon-reload
i can start with
systemctl start pure-ftpd
or
/etc/init.d/pure-ftpd start
and i can connect to the server with tls
but i don't think this is the goal.

Regards
Dieter
Comment 3 Stig-Ørjan Smelror 2018-02-11 00:59:43 CET 
Hi again.

I think I found the error. A new version has been pushed and will be available in updates_testing, awaiting validation from QA.

Cheers,
Stig
Stig-Ørjan Smelror 2018-02-11 01:05:13 CET

Depends on: (none) => 22574

Comment 4 Luca Olivetti 2018-02-13 09:51:10 CET 
I too had to modify the init script like comment 2

CC: (none) => luca

Comment 6 Stig-Ørjan Smelror 2018-02-13 10:13:37 CET 
Thank you Luca.

A new, updated package is now in QA for validation. There were quite a few issues that has now been resolved.

Cheers,
Stig
Comment 7 Stig-Ørjan Smelror 2018-03-12 11:00:40 CET 
Package validated and available in core/updates.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

play game 2019-03-27 16:57:17 CET

CC: (none) => thanos17997
Note You need to log in before you can comment on or make changes to this bug.