Author Topic: Enabling FTPs or FPTes  (Read 1195 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Enabling FTPs or FPTes
« on: June 15, 2021, 02:51:05 AM »
I dont know which one is better. FTPs or FTPes. But as I know, it need TLS for the FTP.
I tried to follow the instruction at http://wiki.centos-webpanel.com/how-to-install-tls-for-ftp
It said it can use sh /scripts/install_pure-ftpd_tls if using Centos 7 and CWP version 0.9.8.757+. I used Centos 7 and latest CWP Pro version.
I run that sh command, it said it was installed successfully. But then what need to do? how can I know the FTPs and FTPes can be used?

I read the instruction above, it said to check:
/etc/pki/tls/private/hostname.key
/etc/pki/tls/certs/hostname.crt

I have /etc/pki/tls/certs/hostname.key at my vps, but I didnt see /etc/pki/tls/certs/hostname.crt.

So, how exactly enabling FTPs and FTPes?

Thanks.

Offline
*
Re: Enabling FTPs or FPTes
« Reply #1 on: June 15, 2021, 08:50:58 AM »
You need to create SSL certificate for TLS - something like
Code: [Select]
/etc/certs/pure-ftpd.pem or whatever you have defined as the existence of your cert in
Code: [Select]
/etc/pure-ftpd/pureftpd.conf
something like
Code: [Select]
CertFile   /etc/certs/pure-ftpd.pem
« Last Edit: June 15, 2021, 08:56:45 AM by josephgodwinke »
Applications Developer | RHEL Linux Server Administrator

Offline
*
Re: Enabling FTPs or FPTes
« Reply #2 on: June 16, 2021, 04:19:33 AM »
You need to create SSL certificate for TLS - something like
Code: [Select]
/etc/certs/pure-ftpd.pem or whatever you have defined as the existence of your cert in
Code: [Select]
/etc/pure-ftpd/pureftpd.conf
something like
Code: [Select]
CertFile   /etc/certs/pure-ftpd.pem

In the /etc/pure-ftpd/pure-ftpd.conf, the Cert file is CertFile /etc/pki/tls/private/hostname.pem
And that file is exist.
But what I should do next? I want to force my customer just login to FTPs or FTPes only, and disable plain FTP.

Which part of my pure-ftpd.conf that I have to modify?
Thanks.


Offline
*
Re: Enabling FTPs or FPTes
« Reply #3 on: June 16, 2021, 07:41:55 PM »
Set this in
Code: [Select]
vsftpd.conf
Code: [Select]
ssl_enable=YES
# do not allow anonymous users to access ftp
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES
# enable tlsv1 encryption
ssl_tlsv1=YES
ssl_sslv2=NO
ssl_sslv3=NO
# disallow ssl reuse
require_ssl_reuse=NO
ssl_ciphers=HIGH
rsa_cert_file=/etc/vsftpd.pem
rsa_private_key_file=/etc/vsftpd.pem
# port range for passive mode
pasv_max_port=65535
pasv_min_port=64000
Applications Developer | RHEL Linux Server Administrator

Offline
*
Re: Enabling FTPs or FPTes
« Reply #4 on: June 17, 2021, 05:00:58 AM »
Set this in
Code: [Select]
vsftpd.conf
Code: [Select]
ssl_enable=YES
# do not allow anonymous users to access ftp
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES
# enable tlsv1 encryption
ssl_tlsv1=YES
ssl_sslv2=NO
ssl_sslv3=NO
# disallow ssl reuse
require_ssl_reuse=NO
ssl_ciphers=HIGH
rsa_cert_file=/etc/vsftpd.pem
rsa_private_key_file=/etc/vsftpd.pem
# port range for passive mode
pasv_max_port=65535
pasv_min_port=64000

Dear Joseph,

CWP uses pure-ftpd with the file location
Code: [Select]
/etc/pure-ftpd/pure-ftpd.conf
Is it same with vsftpd? and where is the config file of vsftp location?
Thanks.

Offline
*
Re: Enabling FTPs or FPTes
« Reply #5 on: June 17, 2021, 10:01:43 AM »
No for pureftpd just
Code: [Select]
vi /etc/pure-ftpd/pure-ftpd.conf and add the changes below:


Code: [Select]
# This option accepts three values:
# 0: disable SSL/TLS encryption layer (default).
# 1: accept both cleartext and encrypted sessions.
# 2: refuse connections that don't use the TLS security mechanism,
#    including anonymous sessions.
# Do _not_ uncomment this blindly. Double check that:
# 1) The server has been compiled with TLS support (--with-tls),
# 2) A valid certificate is in place,
# 3) Only compatible clients will log in.
TLS                          2
# Cipher suite for TLS sessions.
# The default suite is secure and setting this property is usually
# only required to *lower* the security to cope with legacy clients.
# Prefix with -C: in order to require valid client certificates.
# If -C: is used, make sure that clients' public keys are present on
# the server.
# TLSCipherSuite               HIGH
CertFile                     /etc/ssl/private/pure-ftpd.pem
CertFileAndKey               "/etc/pure-ftpd.pem" "/etc/pure-ftpd.key"
# Listen only to IPv4 addresses in standalone mode (ie. disable IPv6)
# By default, both IPv4 and IPv6 are enabled.
# IPV4Only                     yes
# Listen only to IPv6 addresses in standalone mode (i.e. disable IPv4)
# By default, both IPv4 and IPv6 are enabled.
# IPV6Only                     yes
« Last Edit: June 17, 2021, 10:05:58 AM by josephgodwinke »
Applications Developer | RHEL Linux Server Administrator

Offline
*
Re: Enabling FTPs or FPTes
« Reply #6 on: June 18, 2021, 04:23:26 AM »
Dear Joseph,

Thanks for your help.
I have checked my pure-ftpd.conf.
The line
Code: [Select]
CertFile                     /etc/ssl/private/pure-ftpd.pem
CertFileAndKey               "/etc/pure-ftpd.pem" "/etc/pure-ftpd.key"
is not same with mine.
My conf file contains:

Code: [Select]
TLSCipherSuite HIGH:MEDIUM:+TLSv1:!SSLv2:!SSLv3
CertFile /etc/pki/tls/private/hostname.pem

There is no line:
Code: [Select]
CertFileAndKey               "/etc/pure-ftpd.pem" "/etc/pure-ftpd.key"
And these files do not exist in my vps:
Quote
/etc/ssl/private/pure-ftpd.pem
/etc/pure-ftpd.pem
/etc/pure-ftpd.key

What should I do? And should TLSCipherSuite need to be changed to TLS 1.2?

Thanks.

Offline
*
Re: Enabling FTPs or FPTes
« Reply #7 on: June 18, 2021, 01:23:32 PM »
post the contents of your pure-ftpd.conf
Applications Developer | RHEL Linux Server Administrator

Offline
*
Re: Enabling FTPs or FPTes
« Reply #8 on: June 19, 2021, 02:34:55 AM »
post the contents of your pure-ftpd.conf
Dear Joseph,

here it is all content of my pure-ftpd.conf

Code: [Select]
############################################################
#                                                          #
#             Configuration file for pure-ftpd             #
#                                                          #
############################################################

# If you want to run Pure-FTPd with this configuration
# instead of command-line options, please run the
# following command :
#
# /usr/sbin/pure-ftpd /etc/pure-ftpd/pure-ftpd.conf
#
# Online documentation:
# https://www.pureftpd.org/project/pure-ftpd/doc


# Restrict users to their home directory

ChrootEveryone               yes



# If the previous option is set to "no", members of the following group
# won't be restricted. Others will be. If you don't want chroot()ing anyone,
# just comment out ChrootEveryone and TrustedGID.

# TrustedGID                   100



# Turn on compatibility hacks for broken clients

BrokenClientsCompatibility   no



# Maximum number of simultaneous users

MaxClientsNumber             50



# Run as a background process

Daemonize                    yes



# Maximum number of simultaneous clients with the same IP address

MaxClientsPerIP              8



# If you want to log all client commands, set this to "yes".
# This directive can be specified twice to also log server responses.

VerboseLog                   no



# List dot-files even when the client doesn't send "-a".

DisplayDotFiles              yes



# Disallow authenticated users - Act only as a public FTP server.

AnonymousOnly                no



# Disallow anonymous connections. Only accept authenticated users.

NoAnonymous                  no



# Syslog facility (auth, authpriv, daemon, ftp, security, user, local*)
# The default facility is "ftp". "none" disables logging.

SyslogFacility               ftp



# Display fortune cookies

# FortunesFile                 /usr/share/fortune/zippy



# Don't resolve host names in log files. Recommended unless you trust
# reverse host names, and don't care about DNS resolution being possibly slow.

DontResolve                  yes



# Maximum idle time in minutes (default = 15 minutes)

MaxIdleTime                  15



# LDAP configuration file (see README.LDAP)

# LDAPConfigFile                /etc/pure-ftpd/pureftpd-ldap.conf



# MySQL configuration file (see README.MySQL)

# MySQLConfigFile               /etc/pure-ftpd/pureftpd-mysql.conf


# PostgreSQL configuration file (see README.PGSQL)

# PGSQLConfigFile               /etc/pure-ftpd/pureftpd-pgsql.conf


# PureDB user database (see README.Virtual-Users)

PureDB /etc/pure-ftpd/pureftpd.pdb


# Path to pure-authd socket (see README.Authentication-Modules)

# ExtAuth                       /var/run/ftpd.sock



# If you want to enable PAM authentication, uncomment the following line

PAMAuthentication    yes



# If you want simple Unix (/etc/passwd) authentication, uncomment this

UnixAuthentication       yes



# Please note that LDAPConfigFile, MySQLConfigFile, PAMAuthentication and
# UnixAuthentication can be used specified once, but can be combined
# together. For instance, if you use MySQLConfigFile, then UnixAuthentication,
# the SQL server will be used first. If the SQL authentication fails because the
# user wasn't found, a new attempt will be done using system authentication.
# If the SQL authentication fails because the password didn't match, the
# authentication chain stops here. Authentication methods are chained in
# the order they are given.



# 'ls' recursion limits. The first argument is the maximum number of
# files to be displayed. The second one is the max subdirectories depth.

LimitRecursion               10000 8



# Are anonymous users allowed to create new directories?

AnonymousCanCreateDirs       no



# If the system load is greater than the given value, anonymous users
# aren't allowed to download.

MaxLoad                      4



# Port range for passive connections - keep it as broad as possible.

# PassivePortRange             30000 50000



# Force an IP address in PASV/EPSV/SPSV replies. - for NAT.
# Symbolic host names are also accepted for gateways with dynamic IP
# addresses.

# ForcePassiveIP               192.168.0.1



# Upload/download ratio for anonymous users.

# AnonymousRatio               1 10



# Upload/download ratio for all users.
# This directive supersedes the previous one.

# UserRatio                    1 10



# Disallow downloads of files owned by the "ftp" system user;
# files that were uploaded but not validated by a local admin.

AntiWarez                    yes



# IP address/port to listen to (default=all IP addresses, port 21).

# Bind                         127.0.0.1,21



# Maximum bandwidth for anonymous users in KB/s

# AnonymousBandwidth           8



# Maximum bandwidth for *all* users (including anonymous) in KB/s
# Use AnonymousBandwidth *or* UserBandwidth, not both.

# UserBandwidth                8



# File creation mask. <umask for files>:<umask for dirs> .
# 177:077 if you feel paranoid.

Umask                        133:022



# Minimum UID for an authenticated user to log in.
# For example, a value of 100 prevents all users whose user id is below
# 100 from logging in. If you want "root" to be able to log in, use 0.

MinUID                      1000



# Do not use the /etc/ftpusers file to disable accounts. We're already
# using MinUID to block users with uid < 1000

UseFtpUsers no



# Allow FXP transfers for authenticated users.

AllowUserFXP                 no



# Allow anonymous FXP for anonymous and non-anonymous users.

AllowAnonymousFXP            no



# Users can't delete/write files starting with a dot ('.')
# even if they own them. But if TrustedGID is enabled, that group
# will exceptionally have access to dot-files.

ProhibitDotFilesWrite        no



# Prohibit *reading* of files starting with a dot (.history, .ssh...)

ProhibitDotFilesRead         no



# Don't overwrite files. When a file whose name already exist is uploaded,
# it gets automatically renamed to file.1, file.2, file.3, ...

AutoRename                   no



# Prevent anonymous users from uploading new files (no = upload is allowed)

AnonymousCantUpload         yes



# Only connections to this specific IP address are allowed to be
# non-anonymous. You can use this directive to open several public IPs for
# anonymous FTP, and keep a private firewalled IP for remote administration.
# You can also only allow a non-routable local IP (such as 10.x.x.x) for
# authenticated users, and run a public anon-only FTP server on another IP.

# TrustedIP                    10.1.1.1



# To add the PID to log entries, uncomment the following line.

# LogPID                       yes



# Create an additional log file with transfers logged in a Apache-like format :
# fw.c9x.org - jedi [13/Apr/2017:19:36:39] "GET /ftp/linux.tar.bz2" 200 21809338
# This log file can then be processed by common HTTP traffic analyzers.

AltLog                     clf:/var/log/pureftpd.log



# Create an additional log file with transfers logged in a format optimized
# for statistic reports.

# AltLog                     stats:/var/log/pureftpd.log



# Create an additional log file with transfers logged in the standard W3C
# format (compatible with many HTTP log analyzers)

# AltLog                     w3c:/var/log/pureftpd.log



# Disallow the CHMOD command. Users cannot change perms of their own files.

# NoChmod                      yes



# Allow users to resume/upload files, but *NOT* to delete them.

# KeepAllFiles                 yes



# Automatically create home directories if they are missing

# CreateHomeDir                yes



# Enable virtual quotas. The first value is the max number of files.
# The second value is the maximum size, in megabytes.
# So 1000:10 limits every user to 1000 files and 10 MB.

# Quota                        1000:10



# If your pure-ftpd has been compiled with standalone support, you can change
# the location of the pid file. The default is /var/run/pure-ftpd.pid

#PIDFile                     /var/run/pure-ftpd.pid



# If your pure-ftpd has been compiled with pure-uploadscript support,
# this will make pure-ftpd write info about new uploads to
# /var/run/pure-ftpd.upload.pipe so pure-uploadscript can read it and
# spawn a script to handle the upload.
# Don't enable this option if you don't actually use pure-uploadscript.

# CallUploadScript             yes



# This option is useful on servers where anonymous upload is
# allowed. When the partition is more that percententage full,
# new uploads are disallowed.

MaxDiskUsage                   99



# Set to 'yes' to prevent users from renaming files.

# NoRename                     yes



# Be 'customer proof': forbids common customer mistakes such as
# 'chmod 0 public_html', that are valid, but can cause customers to
# unintentionally shoot themselves in the foot.

CustomerProof                yes



# Per-user concurrency limits. Will only work if the FTP server has
# been compiled with --with-peruserlimits.
# Format is: <max sessions per user>:<max anonymous sessions>
# For example, 3:20 means that an authenticated user can have up to 3 active
# sessions, and that up to 20 anonymous sessions are allowed.

# PerUserLimits                3:20



# When a file is uploaded and there was already a previous version of the file
# with the same name, the old file will neither get removed nor truncated.
# The file will be stored under a temporary name and once the upload is
# complete, it will be atomically renamed. For example, when a large PHP
# script is being uploaded, the web server will keep serving the old version and
# later switch to the new one as soon as the full file will have been
# transferred. This option is incompatible with virtual quotas.

# NoTruncate                   yes



# This option accepts three values:
# 0: disable SSL/TLS encryption layer (default).
# 1: accept both cleartext and encrypted sessions.
# 2: refuse connections that don't use the TLS security mechanism,
#    including anonymous sessions.
# Do _not_ uncomment this blindly. Double check that:
# 1) The server has been compiled with TLS support (--with-tls),
# 2) A valid certificate is in place,
# 3) Only compatible clients will log in.

# TLS                          1


# Cipher suite for TLS sessions.
# The default suite is secure and setting this property is usually
# only required to *lower* the security to cope with legacy clients.
# Prefix with -C: in order to require valid client certificates.
# If -C: is used, make sure that clients' public keys are present on
# the server.

# TLSCipherSuite               HIGH



# Certificate file, for TLS

# CertFile                     /etc/ssl/private/pure-ftpd.pem



# Listen only to IPv4 addresses in standalone mode (ie. disable IPv6)
# By default, both IPv4 and IPv6 are enabled.

# IPV4Only                     yes



# Listen only to IPv6 addresses in standalone mode (i.e. disable IPv4)
# By default, both IPv4 and IPv6 are enabled.

# IPV6Only                     yes



# UTF-8 support for file names (RFC 2640)
# Set the charset of the server filesystem and optionally the default charset
# for remote clients that don't use UTF-8.
# Works only if pure-ftpd has been compiled with --with-rfc2640

# FileSystemCharset                big5
# ClientCharset                    big5
TLS 1
TLSCipherSuite HIGH:MEDIUM:+TLSv1:!SSLv2:!SSLv3
CertFile /etc/pki/tls/private/hostname.pem

Thanks.