Skip to main content

Get SSL Certificate (Let's Encrypt)

 Get SSL Certificates from Let's Encrypt who provides Free SSL Certificates.

Refer to the details for Let's Encrypt official site below.

⇒ https://letsencrypt.org/

By the way, expiration date of a cert is 90 days, so you must update within next 90 days later.

[1]. Install Certbot Client which is the tool to get certificates from Let's Encrypt.

[root@dlp ~]# dnf module -y install python36

[root@dlp ~]# dnf -y install gcc mod_ssl python3-virtualenv redhat-rpm-config augeas-libs libffi-devel openssl-devel

[root@dlp ~]# curl -O https://dl.eff.org/certbot-auto

[root@dlp ~]# mv certbot-auto /usr/local/bin/

[root@dlp ~]# chmod 700 /usr/local/bin/certbot-auto

[2]. Get certificates.

It needs Web server like Apache httpd or Nginx must be runing on the server you work.

If no Web server is running, skip this section and Refer to [3] section.

Furthermore, it needs that it's possible to access from the Internet to your working server on port 80 because of verification from Let's Encrypt.

# for the option [--webroot], use a directory under the webroot on your server as a working temp

# -w [document root] -d [FQDN you'd like to get certs]

# FQDN (Fully Qualified Domain Name) : Hostname.Domainname

# if you'd like to get certs for more than 2 FQDNs, specify all like below

# ex : if get [srv.world] and [dlp.srv.world]

# ⇒ -d srv.world -d dlp.srv.world

[root@dlp ~]# certbot-auto certonly --webroot -w /var/www/html -d dlp.srv.world

Bootstrapping dependencies for RedHat-based OSes that will use Python3... (you can skip this with --no-bootstrap)

dnf is /usr/bin/dnf

dnf is hashed (/usr/bin/dnf)

.....

.....

# for only initial using, register your email address and agree to terms of use

# specify valid email address

Enter email address (used for urgent renewal and security notices) 

(Enter 'c' to cancel): root@mail.srv.world 


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Please read the Terms of Service at

https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must

agree in order to register with the ACME server at

https://acme-v02.api.letsencrypt.org/directory

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

# agree to the terms of use

(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 our work

encrypting the web, EFF news, campaigns, and ways to support digital freedom.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(Y)es/(N)o: Y

Obtaining a new certificate

Performing the following challenges:

http-01 challenge for dlp.srv.world

Using the webroot path /var/www/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/dlp.srv.world/fullchain.pem

   Your key file has been saved at:

   /etc/letsencrypt/live/dlp.srv.world/privkey.pem

   Your cert will expire on 2020-03-17. To obtain a new or tweaked

   version of this certificate in the future, simply run certbot-auto

   again. To non-interactively renew *all* of your certificates, run

   "certbot-auto 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


# success if [Congratulations] is shown

# certs are created under the [/etc/letsencrypt/live/(FQDN)/] directory


# cert.pem       ⇒ SSL Server cert(includes public-key)

# chain.pem      ⇒ intermediate certificate

# fullchain.pem  ⇒ combined file cert.pem and chain.pem

# privkey.pem    ⇒ private-key file

[3]. If no Web Server is running on your working server, it's possbile to get certs with using Certbot's Web Server feature. Anyway, it needs that it's possible to access from the Internet to your working server on port 80 because of verification from Let's Encrypt.

# for the option [--standalone], use Certbot's Web Server feature

# -d [FQDN you'd like to get certs]

# FQDN (Fully Qualified Domain Name) : Hostname.Domainname

# if you'd like to get certs for more than 2 FQDNs, specify all like below

# ex : if get [srv.world] and [mail.srv.world] ⇒ -d srv.world -d mail.srv.world

[root@dlp ~]# certbot-auto certonly --standalone -d mail.srv.world

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Plugins selected: Authenticator standalone, Installer None

Obtaining a new certificate

Performing the following challenges:

http-01 challenge for mail.srv.world

Waiting for verification...

Cleaning up challenges


IMPORTANT NOTES:

 - Congratulations! Your certificate and chain have been saved at:

   /etc/letsencrypt/live/mail.srv.world/fullchain.pem

   Your key file has been saved at:

   /etc/letsencrypt/live/mail.srv.world/privkey.pem

   Your cert will expire on 2020-03-17. To obtain a new or tweaked

   version of this certificate in the future, simply run certbot-auto

   again. To non-interactively renew *all* of your certificates, run

   "certbot-auto renew"

 - 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

[4]. For Updating existing certs, Do like follows.

# update all certs which has less than 30 days expiration

# if you'd like to update certs which has more than 30 days expiration, add [--force-renew] option

[root@dlp ~]# certbot-auto renew

[5] If you'd like to convert certificates to PKCS12 (PFX) format for Windows, do like follows.

[root@dlp ~]# openssl pkcs12 -export -in fullchain.pem -inkey privkey.pem -out dlp_for_iis.pfx

Enter Export Password:     # set any export password

Verifying - Enter Export Password:


Comments

Post a Comment

Popular posts from this blog

Lambda Function with Amazon SNS

  Amazon SNS is a service used for push notification. In this chapter, we will explain working of AWS Lambda and Amazon SNS with the help of an example where will perform the following actions − Create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch Send SNS text message on phone number given. Requisites To create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch, we need not follow the steps given below − Create Topic in SNS Create Role for permission in IAM Create AWS Lambda Function Publish to topic to activate trigger Check the message details in CloudWatch service. To send SNS text message on phone number given, we need to do the following − Add code in AWS Lambda to send message to your phone. Example In this example, we will create a topic in SNS. When details are entered in the topic to publish, AWS Lambda is triggered. The topic details are logged in CloudWatch and a message is sent on phone by AWS Lambda. Here is a basic block diagram which exp
Post a Comment
Read more

Unix / Linux - Shell Functions

W e will discuss in detail about the shell functions. Functions enable you to break down the overall functionality of a script into smaller, logical subsections, which can then be called upon to perform their individual tasks when needed. Using functions to perform repetitive tasks is an excellent way to create  code reuse . This is an important part of modern object-oriented programming principles. Shell functions are similar to subroutines, procedures, and functions in other programming languages. Creating Functions To declare a function, simply use the following syntax − function_name () { list of commands } The name of your function is  function_name , and that's what you will use to call it from elsewhere in your scripts. The function name must be followed by parentheses, followed by a list of commands enclosed within braces. Example Following example shows the use of function − #!/bin/sh # Define your function here Hello () { echo "Hello World" } # Invoke yo
Post a Comment
Read more

Unix / Linux - Shell Input/Output Redirections

W e will discuss in detail about the Shell input/output redirections. Most Unix system commands take input from your terminal and send the resulting output back to your terminal. A command normally reads its input from the standard input, which happens to be your terminal by default. Similarly, a command normally writes its output to standard output, which is again your terminal by default. Output Redirection The output from a command normally intended for standard output can be easily diverted to a file instead. This capability is known as output redirection. If the notation > file is appended to any command that normally writes its output to standard output, the output of that command will be written to file instead of your terminal. Check the following  who  command which redirects the complete output of the command in the users file. $ who > users Notice that no output appears at the terminal. This is because the output has been redirected from the default standard output dev
Post a Comment
Read more