Project Talk:LibreSSL

From Gentoo Wiki
Jump to: navigation, search
Note
This is a talk page. Please add newer comments below older ones, and sign your comments using four tildes (~~~~). When adding a new section (at the bottom of the page), please mark it as "open for discussion" by using {{talk|open}} so it will show up in the list of open discussions.

typos

Talk status
This discussion is still ongoing.

(We'll skip libressl-2.3.x for now since it drops SSLv3 support which man packages still use. If you want to do testing with 2.3.x then keyword it instead below.)

change that to:

(We'll skip libressl-2.3.x for now since it drops SSLv3 support which many packages still use. If you want to do testing with 2.3.x then keyword it instead below.) unless you intended it to be a specific man pages package, which I find unlikely.

ng0 (talk) 12:39, 1 June 2016 (UTC)

The issue is moot, I think. Checking available packages, dev-libs/libressl-2.2 is no longer available. The whole portion needs to be rewritten.
--Pepoluan (talk) 16:36, 7 August 2016 (UTC)

suggestions

Talk status
This discussion is still ongoing.

Mention variables like CURL_SSL in the section about how to switch a box to libressl.

That one in particular is important because not changing CURL_SSL when doing USE=libressl blocks dev-vcs/git.

Outdated information

Talk status
This discussion is still ongoing.
root # mkdir -p /etc/portage/profile

per emerge's own man page, it's /etc/portage/profiles.

root # echo "dev-libs/openssl" >> /etc/portage/package.mask
  1. /etc/portage/package.mask is a directory
  2. again, per emerge's man page, package.mask goes in /etc/portage/profiles.

This is on the Gentoo release of June 5th 2017.

I am not sure as to which is correct, but I am inclined to follow the man page. Correct me on anything that might be inaccurate.

Best regards,

Emegir (talk) 21:36, 13 June 2017 (UTC)

CURL_SSL

Talk status
This discussion is still ongoing as of 2017-11-18.

CURL_SSL seems to default to CURL_SSL="openssl", there probably should be added something about it. Lanodan (talk) 21:10, 18 November 2017 (UTC)

I'd like to second (third?) This recommendation. The system set depends on curl, so it is definitely necessary. This can be fixed easily by changing:

root #echo 'USE="${USE} libressl"' >> /etc/portage/make.conf
root #mkdir -p /etc/portage/profile
root #echo "-libressl" >> /etc/portage/profile/use.stable.mask
root #echo "dev-libs/openssl" >> /etc/portage/package.mask
root #echo "=dev-libs/libressl-2.2*" >> /etc/portage/package.accept_keywords

to:

root #echo 'USE="${USE} libressl"' >> /etc/portage/make.conf
root #echo 'CURL_SSL="libressl"' >> /etc/portage/make.conf
root #mkdir -p /etc/portage/profile
root #echo "-libressl" >> /etc/portage/profile/use.stable.mask
root #echo "dev-libs/openssl" >> /etc/portage/package.mask
root #echo "=dev-libs/libressl-2.2*" >> /etc/portage/package.accept_keywords

Benchaney (talk) 21:57, 09 March 2018 (UTC)

Add quickpkg

Talk status
This discussion is still ongoing as of 2017-12-09.

Howdy. I'd like to add the following to the User section:

From:

root #emerge -f libressl
root #emerge -C openssl
root #emerge -1q libressl

To:

root #emerge -f libressl
root #quickpkg openssl
root #emerge -C openssl
root #emerge -1q libressl

Just to make recovery less painful. Thanks.

--NightMonkey (talk) 19:49, 9 December 2017 (UTC)

Mask only dev-libs/openssl:0

Talk status
This discussion is still ongoing.

The current page just puts a mask on `dev-libs/openssl`, which also masks binary-compatibility slots like `dev-libs/openssl:0.9.8` which can be installed at the same time. Which I think could also allow to have LibreSSL installed at the same time as a recent OpenSSL. Lanodan (talk) 01:50, 24 February 2019 (UTC)

Diction Correction: build -> built

Talk status
This discussion is still ongoing.
This is worse than some package simply not build against LibreSSL.

change to

This is worse than some package simply not built against LibreSSL.

Jlpoole (talk) 16:28, 29 September 2019 (UTC) jlpoole