SlackwareThis Forum is for the discussion of Slackware Linux.
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.
i know the cert is there, i know it can read the file from the dir, i know the cert isnt empty
wtf is going wrong here... i dont have to set anything special in the httpd.conf do i? the mod_ssl is already setup within by default when i installed...
something about that not enough data error.. idk man this is wierd
Last edited by scrupul0us; 02-03-2006 at 10:12 PM.
If I change my cert (overwrite some characters) and stop/start the server my https breaks in a similar way to yours.
Code:
[Sat Feb 04 16:39:43 2006] [error] SSL Library Error: 218529960 error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
[Sat Feb 04 16:39:43 2006] [error] SSL Library Error: 218595386 error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error
Although it's not the same error, it makes me wonder if openssl (or the args to it) caused something incompatible to happen. What do you get if you type:
Code:
# openssl verify /etc/apache/ssl.crt/server.crt
It should show you the info you typed in when you created the cert. The only error I get is:
Code:
error 18 at 0 depth lookup:self signed certificate
I did't expect the command not to work, just trying to figure out what could have gone wrong with it. When I run the `openssl verify` command on an ordinary file, I get the same error that you do:
It seems that something went wrong on the cert generation and although you must be getting sick of this - can you regenerate the key/cert, verify it, stop apache, deploy the key/cert and start apache (don't just restart apache)?
A straight copy is fine as long as they end up with permissions so that the web server can access them - I'm assuming it was created on the same Linux box that it will be used on.
The problems with creating the cert that I saw on google seemed to be grouped into 2 areas. The first was format, ie DOS line endings because it spent time on a windows box and was ftp'ed in the wrong mode. The second was content - errors during creation due to lack of entropy or permission, both of which would cause errors you'd see.
Since you've already gone through pretty much the same steps I have, this is just a double check.
ok... well the dir i created the key and crt in wasnt the one they were supposed to be in... so i moved the crt to the crt dir and the key to the key dir
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.