[SOLVED] Call for testers: SlackBuild Scripts for letsencrypt
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.
Call for testers: SlackBuild Scripts for letsencrypt
I have pushed my letsencrypt SlackBuild script on my personal github account (letsencrypt branch) and have a public beta testing before i push it to SBo.
Basically you need 4 additional new python modules (already submitted to SBo and still in pending) before you can install letsencrypt.
The letsencrypt SlackBuild itself will install apache and nginx plugins in it's default location.
i rebased to the latest SBo updates and bump it to 0.1.0 (public beta). Not really tested against new dependencies, since it was released like 1d ago, but i will do more test this weekend
Traceback (most recent call last):
File "/usr/bin/letsencrypt", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib64/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/pkg_resources.py", line 2603, in <module>
File "/usr/lib64/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/pkg_resources.py", line 666, in require
File "/usr/lib64/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/pkg_resources.py", line 565, in resolve
pkg_resources.DistributionNotFound: six
What's not to like about a "free, automated, and open certificate authority (CA)"?
Thanks for posting about this and the slackbuild willysr. This looks like a great alternative to self-signed certificates. I'm going test drive this over the weekend.
OK ... so using the webroot authentication I was able to receive certificates ... and then I was unable to install them.
Quote:
[Fri Dec 04 15:54:50.002263 2015] [ssl:emerg] [pid 5861:tid 140183934678912] SSL Library Error: error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
[Fri Dec 04 15:56:53.005593 2015] [ssl:emerg] [pid 5882:tid 140143487276928] AH01898: Unable to configure permitted SSL ciphers
[Fri Dec 04 15:56:53.005627 2015] [ssl:emerg] [pid 5882:tid 140143487276928] SSL Library Error: error:0906D06C:PEM routines:PEM_read_bio:no start line (Expecting: DH PARAMETERS) -- Bad file contents or format - or even just a forgotten SSLCertificateKeyFile?
[Fri Dec 04 15:56:53.005640 2015] [ssl:emerg] [pid 5882:tid 140143487276928] SSL Library Error: error:0906D06C:PEM routines:PEM_read_bio:no start line (Expecting: EC PARAMETERS) -- Bad file contents or format - or even just a forgotten SSLCertificateKeyFile?
[Fri Dec 04 15:56:53.005654 2015] [ssl:emerg] [pid 5882:tid 140143487276928] SSL Library Error: error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
Never mind! This was entirely my issue!
All works well ... we only need apache plugin (or comprehensive guide how to make it work!)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.