ottimo grazie mille

questo è quello che avevo scritto
salve,
ho un server CentOS release 6.9 (Final) su aruba, non riesco a capire cosa di fatto devo fare per avere il tutto su https e non http, se i certificati vanno acquistati oppure se si possono avere gratis, come si configura il server.
Oltre a poter configurare il server dalla 22 ho anche webmin e da li vedo dalla sezione Apache Webserver che ho un Server di Default e un Server Virtuale  che fra le cose ho cancellato e ricreato, ma va configurato il virtuale o lo posso proprio cancellare, oppure va configurato quello di default??
questo era!! non ho letto nulla di tutto ciò in quella pagina forse mi sbaglio?

mbe un post è aperto e si intende aperto come non risolto o in ogni caso ancora commentabile, altrimenti come si fa a capire ? la data? io se trovo post aperti commenti fino a quando qualcuno non indica lo stesso come risolto

salve,
ho un server CentOS release 6.9 (Final) su aruba, non riesco a capire cosa di fatto devo fare per avere il tutto su https e non http, se i certificati vanno acquistati oppure se si possono avere gratis, come si configura il server.
Oltre a poter configurare il server dalla 22 ho anche webmin e da li vedo dalla sezione Apache Webserver che ho un Server di Default e un Server Virtuale  che fra le cose ho cancellato e ricreato, ma va configurato il virtuale o lo posso proprio cancellare, oppure va configurato quello di default?? grazie mille

che bello il tempo passa e non me ne accorgo

iptable:
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:allimport - [0:0]
:OUTPUT ACCEPT [0:0]
-A FORWARD -o eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_OUT:
-A FORWARD -i eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_IN:
-A OUTPUT -o eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_OUT:
-A INPUT -i eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_IN:
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 22 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 80 --state NEW -j ACCEPT
# SERVER SICURO 443 HTTPS
-A INPUT -p tcp -m tcp -m state --dport 443 --state NEW -j ACCEPT
-A INPUT -p tcp -m tcp -m state --dport xx000:xxxx --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport x0000 --state NEW -j ACCEPT
# -A INPUT -m state --state NEW -m tcp -p tcp --dport 3306 -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 21 --state NEW -j ACCEPT
-A INPUT -p tcp -m state -m tcp --dport 20 --state NEW -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
# allimport
-A INPUT -p tcp -m tcp -m state --dport x0000 --state NEW -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Generated by webmin
*mangle
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed
# Generated by webmin
*nat
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT



vsftp

# Example config file /etc/vsftpd/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
ftpd_banner=Welcome to my FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd/banned_emails
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
chroot_local_user=YES
#chroot_list_enable=YES
#(default follows)
#chroot_list_file=/etc/vsftpd/chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
listen=YES
#
# This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES

pam_service_name=vsftpd
userlist_enable=YES
#userlist_deny=NO aggiunta da me
userlist_deny=NO
tcp_wrappers=YES

#aggiunto successivamente per ssl
rsa_cert_file=/xxxxxx.pem
rsa_private_key_file=/xxxxxxx.pem
ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES

ssl_tlsv1=YES
ssl_sslv2=NO
ssl_sslv3=NO

require_ssl_reuse=NO
ssl_ciphers=HIGH
#fine aggiunta per ssl

# passive port range
pasv_address=xx.xx.xx.xx
pasv_enable=YES
pasv_max_port=xxxxx
pasv_min_port=xxxxx

salve,
vorrei capire come fare per vedere i log di iptable intendo tutti i tentativi, ad esempio ho installato vsftp esplicito su tls e non riesco a collegarmi quando il firewall è attivo ma non riesco neanche a vedere il log e capire su quali porte viene a bussare o perché cadono i pacchetti.
il tutto è su un cloud aruba e ho impostato una regola:
Pacchetti in ingresso (INPUT)
se il protocollo è TCP e la porta di destinazione è 3000:3999 e lo stato della connessione è NEW (le porte sono un esempio poi sono diverse)
ma niente a firewall attivo non funziona