Skip to contentSkip to conversation

LibreSSL support?

Buildroot Eric Le Bihan 3 participants 4 messages Dec 5, 2016 – Dec 6, 2016

lore
Share & tools
lore
#0 lore raw

Hi all!

Are there any plans for adding support for LibreSSL?

I've found a patch [1] in patchwork, from M. Hadjinlian, posted two years ago. The review concludes with the need for the introduction of a virtual package, as LibreSSL uses the same names for its binaries and libraries as OpenSSL (openssl, libcrypto, libssl and libtls).

So, what would be the best solution:

a)
1. introduce the virtual package openssl-compat.
2. make libressl and openssl provide openssl-compat.
3. update all packages depending on/selecting openssl to depend on/select openssl-compat.

b)
1. rename openssl to openssl-genuine.
2. introduce virtual package openssl.
3. make openssl-genuine and libressl provide openssl.

Comments and suggestions welcome.

[1] https://patchwork.ozlabs.org/patch/398963/

--
ELB

#1 lore raw

Hi Eric, all

Quoted 8 lines · Eric Le Bihan

Hi all!

Are there any plans for adding support for LibreSSL?

I've found a patch [1] in patchwork, from M. Hadjinlian, posted two years ago. The review concludes with the need for the introduction of a virtual package, as LibreSSL uses the same names for its binaries and libraries as OpenSSL (openssl, libcrypto, libssl and libtls).

Well the problem is that LibreSSL is *NOT* a real drop in replacement of OpenSSL, so you would need to add a new package and we need to figure a way to have a generic way to say that a package provide SSL, like we have for GLES or others, and change/replace everything in the package that needs ssl *but* since LibreSSL is not a perfect drop-in, some package won't build with it. So it's on a case by case.

Of course, a good first step, would be to simply add the package and include it with a few packages that works and see how it goes.

Quoted 20 lines

So, what would be the best solution:

a)
1. introduce the virtual package openssl-compat.
2. make libressl and openssl provide openssl-compat.
3. update all packages depending on/selecting openssl to depend on/select openssl-compat.

b)
1. rename openssl to openssl-genuine.
2. introduce virtual package openssl.
3. make openssl-genuine and libressl provide openssl.

Comments and suggestions welcome.

[1] https://patchwork.ozlabs.org/patch/398963/

--
ELB

#2 lore raw
Quoted 11 lines · Maxime Hadjinlian

Hi Eric, all

Quoted 6 lines · Eric Le Bihan

Are there any plans for adding support for LibreSSL?

I've found a patch [1] in patchwork, from M. Hadjinlian, posted two years ago. The review concludes with the need for the introduction of a virtual package, as LibreSSL uses the same names for its binaries and libraries as OpenSSL (openssl, libcrypto, libssl and libtls).

Quoted 6 lines

Well the problem is that LibreSSL is *NOT* a real drop in replacement of OpenSSL, so you would need to add a new package and we need to figure a way to have a generic way to say that a package provide SSL, like we have for GLES or others, and change/replace everything in the package that needs ssl *but* since LibreSSL is not a perfect drop-in, some package won't build with it. So it's on a case by case.

Thanks for pointing this compatibility issue out. The Alpine project made the switch from OpenSSL to LibreSSL [1], so this can be used to get a list of packages which are compatible with either LibreSSL, OpenSSL or both.

[1] http://lists.alpinelinux.org/alpine-devel/5463.html

Best regards,

--
ELB

#3 lore raw
In reply to Maxime Hadjinlian
Quoted 12 lines · Maxime Hadjinlian

Hi Eric, all

Quoted 8 lines · Eric Le Bihan

Hi all!

Are there any plans for adding support for LibreSSL?

I've found a patch [1] in patchwork, from M. Hadjinlian, posted two years ago. The review concludes with the need for the introduction of a virtual package, as LibreSSL uses the same names for its binaries and libraries as OpenSSL (openssl, libcrypto, libssl and libtls).

Quoted 6 lines

Well the problem is that LibreSSL is *NOT* a real drop in replacement of OpenSSL, so you would need to add a new package and we need to figure a way to have a generic way to say that a package provide SSL, like we have for GLES or others, and change/replace everything in the package that needs ssl *but* since LibreSSL is not a perfect drop-in, some package won't build with it. So it's on a case by case.

We have the same with lua/luajit. They are more or less compatible but not
completely. So we add explicit dependencies when necessary, and use the virtual package when both are possible.

I would propose to start with assuming libressl works, and fix autobuild
failures when they occur.

Quoted 16 lines

Of course, a good first step, would be to simply add the package and include it with a few packages that works and see how it goes.

Quoted 13 lines

So, what would be the best solution:

a)
1. introduce the virtual package openssl-compat.
2. make libressl and openssl provide openssl-compat.
3. update all packages depending on/selecting openssl to depend on/select openssl-compat.

b)
1. rename openssl to openssl-genuine.
2. introduce virtual package openssl.
3. make openssl-genuine and libressl provide openssl.

I expect most packages *will* work with libressl, so I think option b is
better. Step 1 and 2 will have to be done in a single patch, BTW, otherwise you have to change all current uses of BR2_PACKAGE_OPENSSL first...

Since there are a lot of 'select BR2_PACKAGE_OPENSSL', you'll have to use a
trick like libjpeg/jpeg-turbo to automatically select one.

Regards,
Arnout

Quoted 12 lines
Quoted 7 lines

Comments and suggestions welcome.

[1] https://patchwork.ozlabs.org/patch/398963/

--
ELB

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF