Skip to main content

How to Generate CSR using Openssl in Linux



Before Generating csr ,let see what is Openssl.
#It is nothing but a core library ,which is used for general purpose in cryptography,it is an open source product which work towards the implementation of SSL and TLS protocols.

Talking about openssl, some people called the certificates generated from openssl as "self signed certificate".

lets go towards now,creating CSR and private key using openssl command,

Just log in to any of your Linux box and run following command as root user replacing the required information as per your need .

[root@SVR home]# openssl req -new -newkey  rsa:2048 -nodes -sha256 -out domain_name.csr -keyout domain_name.key -subj "/C=US/ST=state/L=locality/O=organization/OU=organization unit Dept/CN=www.domain.com"

 You will get output like :





Then check whether ,all the information we have entered ,while creating CSR is proper ,by decoding the CSR from some online tool.

First do the cat to the csr file

[root@SVR home]# cat domain_name.csr


-----BEGIN CERTIFICATE REQUEST-----
MIIDCDCCAfACAQAwgYExCzAJBgNVBAYTAlVTMQ4wDAYDVQQIEwVzdGF0ZTERMA8G
A1UEBxMIbG9jYWxpdHkxFTATBgNVBAoTDG9yZ2FuaXphdGlvbjEfMB0GA1UECxMW
b3JnYW5pemF0aW9uIHVuaXQgRGVwdDEXMBUGA1UEAxMOd3d3LmRvbWFpbi5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC0ePkRLrz4fkMoRf05XAbw
vMQYGltC50cxGYheRprd/wlvqWmWSUaZBoreNR5jYBfZwRGwmGwsPXncJzN6/t/D
+r/Azfvb1wWxqg5QgAU+Gm/igSUM8ihnirFxBXfsIHDA4PNJ0GgM+y1jLnaEPMvP
vNDvPEtOhRcIoGcq6Dnd3x0JJtMp4x0RZ30U0/dbcgNtmrNh3dHMbVcH9/OmeRut
FnnLRmh+OGDlH9OjD5CbEOgk4XK29G6yt1vKQThFRmJ95QE+XSj+BMTq59cgmJ99
MAjj8E21PG44HHknwhi1Jno1tqguT8O8eXxUj8uhazkFbwNIw+bKG6kuBnmhiYdB
AgMBAAGgQTA/BgkqhkiG9w0BCQ4xMjAwMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXg
MBYGA1UdEQQPMA2CC2Rhd2dpbmMuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQBSy4tq
geUihlg+i0c53Y77WXuT5zEngrc3nvdyOcqhVwbzGUKAQJyz9DMc+pRo+rEi8gsN
1PVUgXclH5m7gQQxBcowWJEd7yXAw6ZLnwiNDGpStWbmUaZ5HLH4iM7hD8/8KWC7
ycdLyYg0TrljmizmbGchik5iGk+VIqffebLJkq2L+XkLVMLdMjoowGyZdOcz7BwO
wvhPB1DEOhDbQNiRHS4HVw5dWq79bUgxVPWb8gvVweL3rv2Yx+EdRtHe902kWbiN
12bBFeUNWYfIFARUP/SYvIl9qvTKQ6zgCwK8TRYWMUMJfANA9jEVxP1aibxKU7y2
TKNygZt3ts5arBs6
-----END CERTIFICATE REQUEST-----


Now, to check whether ,you have entered the proper information while creating CSR, we need to check the content of the CSR,for this refer URL

http://www.linuxforeveryone.com/2015_01_01_archive.html


And if you want self signed certificate ,then we can use below openssl command to get a Certificate using csr and private key we have just created. Use below command for this purpose.


openssl x509 -signkey domain_name.key -sha256  -in domain_name.csr -req -days 365 -out domain.crt

Where,

domain_name.key ===== is  private key.
domain_name.csr ===== is csr.
-days ===== Number of days of validity ,you want for your cert.

====================================X============X=================================================

Contact support@linuxforeveryone for any Freelancing work on Linux Servers

Subscribe my YouTube Channel 

Like My Facebook Page 

Browse the Best in class Web Hosting Plans


Comments

Post a Comment

Popular posts from this blog

Solution and Step to fix CVE-2019-5736 Vulnerability - Docker

Recently a new vulnerability has been discovered in the the internet market having target to Docker services. What is this Vulnerability: In short, Docker service uses another service called as runc which is container run time to spawn and run containers. which simply means if docker task is to create docker images then runc task would be running them and attaching a process to container. So as per the recent discovery by the maintainers of runc, the code of this service was having some bug which can be used by attackers to gain the root level of access of the host machine on which docker containers are running. How it can be Exploited: This vulnerability can be exploited in two ways (1) if the docker images are in use is vulnerable making the containers build from it vulnerable also (2) if somehow attacker got the access of containers and then trying to exploit using the bug present in runc and trying to get root privileges. Solution to Fix Vulnerability: Ce

How to Generate CSR using Openssl in Linux

Before Generating CSR ,let see what is Openssl. It is nothing but a core library ,which is used for general purpose in cryptography,it is an open source product which work towards the implementation of SSL and TLS protocols. Talking about openssl, some people called the certificates generated from openssl as "self signed certificate". lets go towards now,creating CSR and private key using openssl command, Just log in to any of your Linux box and run following command as  root user  replacing the required information as per your need . [root@SVR home]#   openssl req -new -newkey  rsa:2048 -nodes -sha256 -out domain_name.csr -keyout domain_name.key -subj "/C=US/ST=state/L=locality/O=organization/OU=organization unit Dept/CN=www.domain.com"  You will get output like : Then check whether ,all the information we have entered ,while creating CSR is proper ,by decoding the CSR from some online tool. First do the cat to the csr file [root@SVR home]#  cat

Multiple instances of redis

In the last post I have covered how to install redis server on Centos/Rhel using rpm method and yum method and some troubleshooting skills. In this post i am going to cover how to install and configure redis to run with multiple ports.                                                                           But why we need more ports ? If you have read my earlier post , you already know that by default redis runs on single port 6379, which any one can use it for small website to cache the data. But for heavy website like magento we need to use additional ports along with 6379 to serve different cache from different ports. Like in Magento there is simple cache which is normally stored under /var/cache directory. Then there is Full Page Cache which is stored under /var/full_page_cache and session cache which is stored under /var/session_cache. Note : Discussion about cache/full page cache/session is not under the scope for this document.