PDA

View Full Version : SLES 12 letsencrypt on SLE_12?



joe_fortier
04-Dec-2015, 18:07
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.

smflood
04-Dec-2015, 18:37
On 04/12/2015 17:14, joe fortier wrote:

> 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.

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.

> 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.

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.
------------------------------------------------------------------------

joe_fortier
04-Dec-2015, 18:57
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:
1) As a "core" like service (lot's of servers will benefit from free true SSL certs) it should not require the SDK
2) 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.

joe_fortier
04-Dec-2015, 20:20
I didn't see your quote in the middle...


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.


Sure.... But the text of the file explicitly mentions SLE12

# SLE12 don't have python-virtualenv
(on the third line).

I'd say they plan to support SLES at some point. But it's (likely?) not as high a priority.

Which is why I'd bring it to the communities attention :-)

malcolmlewis
05-Dec-2015, 03:18
On Fri 04 Dec 2015 07:24:01 PM CST, joe fortier wrote:

I didn't see your quote in the middle...
smflood;30708 Wrote:
>
> 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.
>

Sure.... But the *text* of the file explicitly mentions SLE12

# SLE12 don't have python-virtualenv
(on the third line).

I'd say they plan to support SLES at some point. But it's (likely?) not
as high a priority.

Which is why I'd bring it to the communities attention :-)




Hi
Built it on OBS (and man pages);
https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/letsencrypt
Download;
http://download.opensuse.org/repositories/home:/malcolmlewis:/TESTING/python_SLE_12/noarch/

--
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!

malcolmlewis
05-Dec-2015, 05:11
On Sat 05 Dec 2015 02:18:53 AM CST, malcolmlewis wrote:



On Fri 04 Dec 2015 07:24:01 PM CST, joe fortier wrote:

I didn't see your quote in the middle...
smflood;30708 Wrote:
>
> 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.
>

Sure.... But the *text* of the file explicitly mentions SLE12

# SLE12 don't have python-virtualenv
(on the third line).

I'd say they plan to support SLES at some point. But it's (likely?) not
as high a priority.

Which is why I'd bring it to the communities attention :-)




Hi
Built it on OBS (and man pages);
https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/letsencrypt
Download;
http://download.opensuse.org/repositories/home:/malcolmlewis:/TESTING/python_SLE_12/noarch/



Hi
There is a better build here (lots more dependencies than I
expected...);
https://build.opensuse.org/package/show?project=home%3Aecsos&package=letsencrypt#

Send an email to the user see the address in the changes file asking
to enable a SLE 12 build;
https://build.opensuse.org/package/view_file/home:ecsos/letsencrypt/letsencrypt.changes?expand=1

--
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!