Secure your FTPS server with Let's Encrypt
- ⬅ All articles
- 🗂 Categories
- 🔖 ftp (1)
- 🔖 infrastructure (3)
- 🔖 privacy (1)
- 🔖 compliance (1)
- 🔖 client-side (1)
- 🔖 general (79)
- 🔖 blog (6)
- 🔖 press (2)
- 🔖 australia (1)
- 🔖 client (17)
- 🔖 release (76)
- 🔖 article (14)
- 🔖 security (24)
- 🔖 server (19)
- 🗄 Archive
- 📌 2001 (3)
- 📌 2005 (1)
- 📌 2006 (1)
- 📌 2007 (1)
- 📌 2008 (1)
- 📌 2012 (1)
- 📌 2013 (3)
- 📌 2014 (13)
- 📌 2015 (20)
- 📌 2016 (23)
- 📌 2017 (15)
- 📌 2018 (38)
- 📌 2019 (11)
Thu 29 November 2018 | article
What is Let's Encrypt?
Let's Encrypt (sometimes shortened as LetsEncrypt) is a certificate authority that provides SSL/X.509 certificates at no charge. You can read more on the subject in the Wikipedia article on Let's Encrypt.
A Let's Encrypt certificate is valid for 90 days, but it is recommended to renew it 30 days before expiration.
Certificates are provided using an automated process designed to automate creation, signing, installation, and renewal of certificates for websites in a secure manner.
Only Domain-validated certificates are being issued. Organization-Validated and Extended Validation (EV) Certificates are not available.
How does Let's Encrypt work?
Let's Encrypt uses the Automatic Certificate Management Environment (ACME) protocol.
ACME is a communications protocol for automating interactions between certificate authorities and their users, allowing automated deployments of public key infrastructure (PKI).
SFTPPlus as an ACME client
SFTPPlus implements the client side of the ACME protocol.
It can connect to the Let's Encrypt ACME server, and automatically request SSL/X.509 certificates, free of cost.
To prove that it has administrative rights over a domain, SFTPPlus runs an embedded HTTP server, available over port 80, which implements the HTTP-01 challenge of the ACME protocol.
SFTPPlus can automatically request certificates for HTTPS and FTPS file transfer services, as well as for the Local Manager web console.
The obtained certificates are signed by the Let's Encrypt authority, which is automatically trusted by all modern operating systems. For example, an FTP client using the Windows Certificate Store will automatically accept the certificate used to encrypt a connection to a SFTPPlus server using Let's Encrypt.
All this is done automatically through SFTPPlus' seamless Let's Encrypt integration. You only need to configure the domain name, SFTPPlus will take care of the rest. No need to use external tools like letencrypt.exe, store or copy files in directories like /etc/letsencryt or C:siteswwwroot.
Let's Encrypt and FTPS
While Let's Encrypt was created for HTTPS websites, you can use the same certificate signed by Let's Encrypt's Certificate Authority for FTPS communication.
You can use Let's Encrypt for any secure FTP protocol, be it Explicit FTPS or Implicit FTPS. The certificates can be used over both SSL and TLS, including TLS 1.2.
You still need to have port 80 opened or forwarded to SFTPPlus for the automated certificate generation and renewal.
Check our dedicated documentation page to see how to enable Let's Encrypt for your FTPS server.
This resource is written as of SFTPPlus version 3.42.0.
Evaluating SFTPPlus MFT
The features listed in this article are just a selected few out of many integration and configuration options that are available today. Feel free to talk to the Support team about your requirements with file transfer software.
SFTPPlus MFT Server supports FTP, Explicit FTPS, Implicit FTPS, SFTP, SCP, HTTP and HTTPS.
SFTPPlus MFT is available as an on-premise solution supported on Windows, Linux, AIX, MacOS, Solaris, HP-UX, and FreeBSD.
It is also available on the cloud as Docker containers, AWS or Azure instances and many other cloud providers.
Request a trial using the form below.