Has anyone looked at running the letsencrypt (the free SSL cert group) in SuSE? https://letsencrypt.org/
They just announced open beta.
I’ve installed the application on an ubuntu server platform and it was reasonable painless. But SLES not so much (it’s a beta afterall).
They clearly have SLES on the radar: https://github.com/letsencrypt/letsencrypt/blob/master/bootstrap/_suse_common.sh
but this doesn’t actually work.
I’ve install all the named packages (including using easy_install to install virtualenv) but… no joy. A help output request generates this (with allowances for random tmp file naming):
Command “python setup.py egg_info” failed with error code 1 in /tmp/pip-build-eirG_Z/cffi
This seems an incredibly useful service. We have a lot of one-offs that do not really warrant paying for a cert, but a real cert would certainly (sic) be a nice addition.
On 04/12/2015 17:14, joe fortier wrote:
[color=blue]
Has anyone looked at running the letsencrypt (the free SSL cert group)
in SuSE? https://letsencrypt.org/
They just announced open beta.
I’ve installed the application on an ubuntu server platform and it was
reasonable painless. But SLES not so much (it’s a beta afterall).
They clearly have SLES on the radar: https://github.com/letsencrypt/letsencrypt/blob/master/bootstrap/_suse_common.sh
but this doesn’t actually work.[/color]
If you look at install-deps.sh in the letsencrypt/bootstrap/ you’ll see
that suse.sh is called when openSUSE is detected as the OS and not SLES.
[color=blue]
I’ve install all the named packages (including using easy_install to
install virtualenv) but… no joy. A help output request generates this
(with allowances for random tmp file naming):
Command “python setup.py egg_info” failed with error code 1 in
/tmp/pip-build-eirG_Z/cffi
This seems an incredibly useful service. We have a lot of one-offs that
do not really warrant paying for a cert, but a real cert would certainly
(sic) be a nice addition.[/color]
Do you have python-setuptools installed?
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Yep!
It’s kind of annoying, as it requires the SDK addon (for the most part I’ve been able to avoid this on SLE_12).
But it’s not enough.
What I did in a little more detail:
Installed setup_tools
Then used easy_install to install virtualenv
For good measure, also installed pip (again with easy_install).
I’m sure the developers have chosen to use virtualenv to remove dependencies, and make as “seemless” package as they can.
It’s in part their issue (as SLES is clearly on their radar). But it looks like SuSE is not a tier 1 target
But there’s at least to things I think the SLES team might be concerned with:
As a “core” like service (lot’s of servers will benefit from free true SSL certs) it should not require the SDK
Along the same lines, it’s probably a sign that virtualenv should be part of SLE core.
But mostly I wanted to find out if someone else has worked around these issues.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.48-52.27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.48-52.27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
