SSL хостинг на Apache

Приветствую коллеги! Сегодня у нас задача настроить https с использованием бесплатного сертификата от Let’s Encrypt с виртуальным ssl хостингом на веб сервере Apache. Итак, приступим.

Для начала нам необходимо настроить обычный виртуальный хостинг: Установка Ubuntu 16.04 LAMP Server с Apache 2.4, PHP 7 и MariaDB (вместо MySQL), потому что при получении бесплатного сертификата от Let’s Encrypt нам придется подтверждать владение доменом и будет осуществлен запрос на наш домен. Если он будет успешным то домен будет подтвержден, ну и мы получим свой сертификат.

Установим Certbot — официальный клиент от Let’s Encrypt.

Для Ubuntu 14.04/16.04/18.04:

$ sudo apt-get update
$ sudo apt-get install software-properties-common
$ sudo add-apt-repository ppa:certbot/certbot
$ sudo apt-get update
$ sudo apt-get install python-certbot-apache 

Приведем файл ssl.conf к следующему виду:

$ sudo vim /etc/apache2/mods-available/ssl.conf
<IfModule mod_ssl.c>

# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
SSLRandomSeed startup builtin
SSLRandomSeed startup file:/dev/urandom 512
SSLRandomSeed connect builtin
SSLRandomSeed connect file:/dev/urandom 512

##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##

#
# Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl

# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog exec:/usr/share/apache2/ask-for-passphrase

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
# (The mechanism dbm has known memory leaks and should not be used).
#SSLSessionCache dbm:${APACHE_RUN_DIR}/ssl_scache
SSLSessionCache shmcb:${APACHE_RUN_DIR}/ssl_scache(512000)
SSLSessionCacheTimeout 300

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
# (Disabled by default, the global Mutex directive consolidates by default
# this)
#Mutex file:${APACHE_LOCK_DIR}/ssl_mutex ssl-cache

 

# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate. See the
# ciphers(1) man page from the openssl package for list of all available
# options.
# Enable only secure ciphers:
#SSLCipherSuite HIGH:!aNULL
SSLCipherSuite "ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK"

# SSL server cipher order preference:
# Use server priorities for cipher algorithm choice.
# Clients may prefer lower grade encryption. You should enable this
# option if you want to enforce stronger encryption, and can afford
# the CPU cost, and did not override SSLCipherSuite in a way that puts
# insecure ciphers first.
# Default: Off
SSLHonorCipherOrder on

# The protocols to enable.
# Available values: all, SSLv3, TLSv1, TLSv1.1, TLSv1.2
# SSL v2 is no longer supported
SSLProtocol all -SSLv3 -TLSv1

# Allow insecure renegotiation with clients which do not yet support the
# secure renegotiation protocol. Default: Off
#SSLInsecureRenegotiation on

# Whether to forbid non-SNI clients to access name based virtual hosts.
# Default: Off
#SSLStrictSNIVHostCheck On

SSLCompression off

# OCSP Stapling, only in httpd 2.3.3 and later
SSLUseStapling on
SSLStaplingResponderTimeout 5
SSLStaplingReturnResponderErrors off
SSLStaplingCache shmcb:/tmp/stapling_cache(128000)

# HSTS (mod_headers is required) (15768000 seconds = 6 months)
Header always set Strict-Transport-Security "max-age=15768000"

</IfModule> 

Приводим файл конфигурации sedicomm.com.conf к следующему виду:

$ sudo vim /etc/apache2/sites-available/sedicomm.com.conf
<VirtualHost *:80>

ServerAdmin [email protected]

DocumentRoot /home/hosting/sites/sedicomm.com-ssl/public_html

ServerName sedicomm.com
ServerAlias www.sedicomm.com

<Directory /home/hosting/sites/sedicomm.com-ssl/public_html>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Require all granted
</Directory>

Include /etc/phpmyadmin/apache.conf

ErrorLog "/home/hosting/sites/sedicomm.com-ssl/log/sedicomm.com-ssl-error.log"
CustomLog "/home/hosting/sites/sedicomm.com-ssl/log/sedicomm.com-ssl-access.log" common

</VirtualHost>

Если на сервере Apache все хорошо, то приводим ssl файл конфигурации sedicomm.com-ssl.conf к следующему виду:

$ sudo vim /etc/apache2/sites-available/sedicomm.com-ssl.conf
<VirtualHost *:443>

ServerAdmin [email protected]

DocumentRoot /home/hosting/sites/sedicomm.com-ssl/public_html

ServerName sedicomm.com
ServerAlias www.sedicomm.com

<Directory /home/hosting/sites/sedicomm.com-ssl/public_html>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Require all granted
</Directory>

Include /etc/phpmyadmin/apache.conf

SSLEngine on

SSLCertificateFile /etc/letsencrypt/live/sedicomm.com/cert.pem
SSLCertificateChainFile /etc/letsencrypt/live/sedicomm.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sedicomm.com/privkey.pem
SSLCACertificateFile /etc/letsencrypt/live/sedicomm.com/chain.pem

ErrorLog "/home/hosting/sites/sedicomm.com-ssl/log/sedicomm.com-ssl-error.log"
CustomLog "/home/hosting/sites/sedicomm.com-ssl/log/sedicomm.com-ssl-access.log" common

</VirtualHost>

После внесения изменений в конфигурацию, необходимо перезапустить службу:

$ sudo apachectl -k restart 

Запрашиваем сертификат от Let’s Encrypt:

sudo certbot --webroot -w /home/hosting/sites/sedicomm.com-ssl/public_html/ -d sedicomm.com -d www.sedicomm.com certonly

Скрипт спросит имейл для управления сертификатом —  его необходимо аккуратно ввести, далее необходимо согласиться с лицензионным соглашением. В противном случае настройка на сервере Apache не получится.

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
cancel):[email protected]

-------------------------------------------------------------------------------
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf. You must agree
in order to register with the ACME server at
https://acme-v01.api.letsencrypt.org/directory
-------------------------------------------------------------------------------
(A)gree/(C)ancel: A

-------------------------------------------------------------------------------
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about EFF and
our work to encrypt the web, protect its users and defend digital rights.
-------------------------------------------------------------------------------
(Y)es/(N)o: Y
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for sedicomm.com
http-01 challenge for www.sedicomm.com
Using the webroot path /home/hosting/sites/sedicomm.com-ssl/public_html for all unmatched domains.
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at
/etc/letsencrypt/live/sedicomm.com/fullchain.pem. Your cert will
expire on 2017-10-31. To obtain a new or tweaked version of this
certificate in the future, simply run certbot again. To
non-interactively renew *all* of your certificates, run "certbot
renew"
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
- If you like Certbot, please consider supporting our work by:

Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-le

Проверяем — сертификаты есть:

$ ls -l /etc/letsencrypt/live/sedicomm.com/
total 4
lrwxrwxrwx 1 root root 36 Aug 3 02:19 cert.pem -> ../../archive/sedicomm.com/cert1.pem
lrwxrwxrwx 1 root root 37 Aug 3 02:19 chain.pem -> ../../archive/sedicomm.com/chain1.pem
lrwxrwxrwx 1 root root 41 Aug 3 02:19 fullchain.pem -> ../../archive/sedicomm.com/fullchain1.pem
lrwxrwxrwx 1 root root 39 Aug 3 02:19 privkey.pem -> ../../archive/sedicomm.com/privkey1.pem
-rw-r--r-- 1 root root 543 Aug 3 02:19 README

Необходимо перезапустить службу на веб сервере Apache:

$ sudo apachectl -k restart 

Захдим на сайт, проверяем сертификаты:

Все работает, круто!

Настроим автоматическое обновление сертификата с помощью планировщика заданий cron:

$ sudo crontab -e 

Добавим задания: каждый понедельник в 4:15 утра обновляем сертификат, через две минуты перезапускаем службу на веб сервере Apache. Сертификат обновится если строк действия истекает менее чем за 30 дней:

15 4 * * 1 /usr/bin/certbot renew >> /var/log/le-renew.log
17 4 * * 1 /usr/sbin/apachectl -k restart

Для проверки работы ssl и правильности установки сертификата воспользуемся сайтом Qualys SSL Labs https://www.ssllabs.com/ssltest/:

Таким образом, с поставленной задачей на сервере Apache я справился.

Спасибо за уделенное время на прочтение статьи!

Если возникли вопросы, задавайте их в комментариях.

Подписывайтесь на обновления нашего Блога и оставайтесь в курсе новостей мира инфокоммуникаций!

Чтобы знать больше и выделяться знаниями среди толпы IT-шников, записывайтесь на курсы Cisco от Академии Cisco, курсы Linux от Linux Professional Institute на платформе SEDICOMM University.