3 ms·

I recently built LibreSSL to replace OpenSSL on my laptop that runs ArchLinux. After installing, pretty much every thing works seamlessly so far. I rebuilt pyth

by marios 10y ago

I recently built LibreSSL to replace OpenSSL on my laptop that runs ArchLinux. After installing, pretty much every thing works seamlessly so far. I rebuilt python because apparently the ssl module looks for RAND_egd (or something of the vein that LibreSSL has removed - and I didn't compile it with a shim). Other than that, dig is broken on my system ("ENGINE_by_id failed") although I have not bothered to fix it since drill works fine. It's nice to see LibreSSL being picked up by Linux distributions. I wish other major distros did this (I'm looking at you Debian). IIRC, Alpine was often used to built docker images. If that's still the case, I'd say it's good news.

guitarbill 10y ago
It does seem like a very practical solution. Hopefully we'll see this in the bigger distros once the smaller distros prove it's doable.
microcolonel 10y ago
Worried about OpenSSL, but fine with running drill? ;- ) drill segfaults for me on a regular basis.
- marios 10y ago
  To be fair, I'm not a heavy user of either dig or drill. I use it mostly to check that my local resolver (unbound) is still responding, and that the DHCP distributed resolver isn't handing out garbage. My usage probably falls into the well tested part of the code I guess.
secure 10y ago
> I'm looking at you Debian You can read up on the packaging efforts at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754513 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754513 — there hasn’t been any activity in a while, so if you have something to add, please post there (but please refrain from +1/me too posts).
- voltagex_ 10y ago
  What's the general etiquette regarding "bumping" Debian bugs?
edwintorok 10y ago
There is a LibreSSL overlay in Gentoo, which patches various software that would otherwise fail to build with LibreSSL, currently they are these packages: dev-qt/qtcore dev-qt/qtnetwork net-misc/socat It used to be a bit painful to setup, but things have improved, now I only need this in make.conf: USE="... libressl" CURL_SSL="libressl" And this to mask it: /etc/portage/package.mask/openssl dev-libs/openssl There is still some software that would fail to install (with a conflict between openssl and libressl), but none that I need currently.

by marios 10y ago

guitarbill 10y ago

It does seem like a very practical solution. Hopefully we'll see this in the bigger distros once the smaller distros prove it's doable.

microcolonel 10y ago

Worried about OpenSSL, but fine with running drill? ;- ) drill segfaults for me on a regular basis.

marios 10y ago
To be fair, I'm not a heavy user of either dig or drill. I use it mostly to check that my local resolver (unbound) is still responding, and that the DHCP distributed resolver isn't handing out garbage. My usage probably falls into the well tested part of the code I guess.

secure 10y ago

> I'm looking at you Debian You can read up on the packaging efforts at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754513 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754513 — there hasn’t been any activity in a while, so if you have something to add, please post there (but please refrain from +1/me too posts).

voltagex_ 10y ago
What's the general etiquette regarding "bumping" Debian bugs?

edwintorok 10y ago

There is a LibreSSL overlay in Gentoo, which patches various software that would otherwise fail to build with LibreSSL, currently they are these packages: dev-qt/qtcore dev-qt/qtnetwork net-misc/socat It used to be a bit painful to setup, but things have improved, now I only need this in make.conf: USE="... libressl" CURL_SSL="libressl" And this to mask it: /etc/portage/package.mask/openssl dev-libs/openssl There is still some software that would fail to install (with a conflict between openssl and libressl), but none that I need currently.