Trying to create a Certificate Signing Request with my Certification Authority
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using configuration from openssl-ca.cnf
Error Loading extension section signing_req
140254645262152:error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen('./index.txt.attr','rb')
140254645262152:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:172:
140254645262152:error:0E078072:configuration file routinesEF_LOAD:no such file:conf_def.c:197:
140254645262152:error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen('./index.txt.attr','rb')
You didn't say the procedure used to create you CA, but apparently you miss the index.txt.attr. You can use touch to create the file under the ~/CA directory. You should check openssl-ca.cnf for the correct CA directory location.
FYI you can use the following command to create a key/crt pair without the need of a CA:
Both key and crt are included in the resulting file, so you need to separate them in 2 files (like server.key and server.crt) and use the 2 files as needed.
I am using LetsEncrypt. I have look in ~/ but there is no CA directory in there.
The certificate and key files are located in /etc/pki/tls/certs/ca.crt and /etc/pki/tls/private/ca.key.
That directory contains the following subdirectories:
I went ahead to touched index.txt.attr at the root of the CA directory
You write:
« FYI you can use the following command to create a key/crt pair without the need of a CA.»
Please not tht I am trying to get free https compliance for my website. That's what LetsEncrypt offers. But my configurations attemps haven't resulted to anything yet, for either my main website (http:/www.webafriqa.net) or the affiliated virtual domains.
I am on CentOS 6.8 running Apache 2.2.15 and Sendmail 8.14.4
« FYI you can use the following command to create a key/crt pair without the need of a CA.»
Please not tht I am trying to get free https compliance for my website. That's what LetsEncrypt offers. But my configurations attemps haven't resulted to anything yet, for either my main website (http:/www.webafriqa.net) or the affiliated virtual domains.
Huh, at your OP you said that you're trying to create a self-signed certificate and thus you had a CA problem
FYI, if you want to install a LetsEncrypt certificate, or any other commercial certificate, you don't need a CA. You have to create just the server key and a CSR based on that.
So use your favorite search engine to find a tutorial about using LetsEncrypt for apache on Centos (e.g this one)
Huh, at your OP you said that you're trying to create a self-signed certificate and thus you had a CA problem
FYI, if you want to install a LetsEncrypt certificate, or any other commercial certificate, you don't need a CA. You have to create just the server key and a CSR based on that.
So use your favorite search engine to find a tutorial about using LetsEncrypt for apache on Centos (e.g this one)
Regards
Quote:
Originally Posted by tsbah
Thanks for the clarification and the link.
I'll keep you updated on the result of the LetsEncrypt self-signed certificate creation process.
I have now created the LetsEncrypt self-signed certificate.
Upon restarting httpd the browser displayed the Apache default home page. So, following the instructions I commented out the content of the file located at /etc/httpd/conf.d/welcome.conf.
I got my home page back. However, in the Apache default page the green padlock displayed neatly in the upper left corner of the browser.
That's not the case unfortunately with my real home page.
Just to clear things up a little.
A LetsEncrypt certificate is not self-signed. I haven't use one, but AFAIK it's a perfectly valid SSL certificate like the commercial ones, with the only difference that is free.
That said, I went to the link you've posted and I saw that your certificate is issued for the CN (CommonName that is the actual webserver name) "neene", that is different from your actual CN, that should be "www.webafriqa.net".
In fact going to your site with firefox and getting the cert, I can verify that it's issued for neene!!! and it's indeed self-signed. It's issued on Thu, 09 Mar 2017 (10 days ago) not its not signed by LetsEncrypt.
So most likely you're still using a self-signed cert created by you, and not the one issued by LetsEncrypt.
Ok, I am going through Apache and LetsEncrypt configuration files (httpd.conf. ssl.conf) to try to fix the mismatch error and to standardize on www.webafriqa.net. The idea is to leave neene to host name designation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.