You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FTP over TLS must be used. No clear text connections allowed.
No anonymous activity allowed
Only explicitly defined users are allowed
All ftp connections are chrooted and separate from each other
Base directory in a user's ftp root does not allow write access (this is a chroot side effect). The 'files' subdirectory inside it does.
FTP users are real linux users, not virtual users.
Example playbook
- hosts: ftp-nodesbecome: truegather_facts: truevars:
vsftpd_pasv_min_port: '11000'vsftpd_pasv_max_port: '11999'vsftpd_pasv_address: 8.8.8.8 # The public IP of your server.vsftpd_rsa_cert_file: /path/on/server/tofullchain.pem # This file must already exist on your servervsftpd_rsa_private_key_file: /path/on/server/to/privkey.pem # This file must already exist on your servervsftpd_ini_config_extras: [] # For anything additional config not already handled by the role. See defaults.yml.vsftpd_users:
- username: ftptesterpassword: !vault| $ANSIBLE_VAULT;1.1;AES256 6462343764643764383.....etc.ete.cetcupdate_password: always # Or `on_create`. Only exposed here to allow idempotence tests to pass. Since the salt changes every run, the `user` task always shows as changed, even if the password didn't.roles:
- name: Install vsftpdrole: custom/acromedia.vsftpd