New Install: No TLS on Pure-FTPd

cheers will check it and and confirm whether or not the issue is widespread

 

@EckyBrazzz the initial install log also records the centmin mod modified output for pure-ftpd configuration routine, you can check what was recorded in your initial install's pure-ftpd setup routine using this command

Code (Text):

egrep -rin 'VerboseLog|PureDB|PassivePortRange|TLS ' /root/centminlogs/ | grep -v '#' | grep minimal.log

example output

Code (Text):

egrep -rin 'VerboseLog|PureDB|PassivePortRange|TLS ' /root/centminlogs/ | grep -v '#' | grep minimal.log
/root/centminlogs/installer_170119-224222_minimal.log:12080:VerboseLog                  yes
/root/centminlogs/installer_170119-224222_minimal.log:12082:PureDB                        /etc/pure-ftpd/pureftpd.pdb
/root/centminlogs/installer_170119-224222_minimal.log:12086:PassivePortRange    30001 50011
/root/centminlogs/installer_170119-224222_minimal.log:12091:TLS                      2
/root/centminlogs/installer_170119-224222_minimal.log:12358:TLS SNI support enabled

 

seems latest pure-ftpd update for centos 7 changed pure-ftpd.conf config formatting so broke my sed replacement edits

Code (Text):

yum history list pure-ftpd
Loaded plugins: fastestmirror, priorities, replace, versionlock
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
   110 | -y update                | 2019-03-21 14:56 | I, U           |   36 EE
    32 | -q -y install pure-ftpd  | 2019-01-18 04:17 | Install        |    3

Code (Text):

yum history info 110 | grep pure-ftpd
    Updated pure-ftpd-1.0.42-3.el7.x86_64                 @epel
   1 warning: /etc/pure-ftpd/pure-ftpd.conf created as /etc/pure-ftpd/pure-ftpd.conf.rpmnew

actual updated pure-ftpd config file was dated Feb 13, 2019.

 

Should be fixed in latest 123.09beta01 updated commits for initial installs now https://community.centminmod.com/threads/fix-pure-ftpd-routine-bug-in-123-09beta01.16975/ and link has instructions for existing installs. Also backported fix to 123.08stable too.

Thanks for the heads up - this new bug needed ironing out for sure