From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Proper action for libtls: /etc/ssl/cert.pem
Date: Mon, 03 May 2021 18:17:30 +0200 [thread overview]
Message-ID: <20210503161730.vuVRkO_ZPYcAh1mlVM-qfAO1dMkHTYCiGgECzRq1Xc0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29299@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Closed issue by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/29299
Description:
- libtls and all of its dependents looks for certs file in `/etc/ssl/cert.pem`
- OpenSSL provides the symlink at `/etc/ssl/certs.pem`
- Old our LibreSSL provides a symlink to `certs.pem` in `/etc/ssl/cert.pem`
In order to make our users' system work, I've provided a temporary fix at ee34f60ecb, (libtls: ship /etc/ssl/cert.pem, 2021-03-08).
I'm not sure if it could be qualified as a permanent fix, or we should patch libtls source to change `cert.pem` into `certs.pem`.
My naive grep in `apps/nc` and `tls` yields 12 occurences of `cert.pem`.
prev parent reply other threads:[~2021-05-03 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 3:00 [ISSUE] " sgn
2021-03-08 3:01 ` sgn
2021-03-08 10:15 ` q66
2021-04-27 23:45 ` ericonr
2021-05-02 11:45 ` sgn
2021-05-03 16:17 ` leahneukirchen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210503161730.vuVRkO_ZPYcAh1mlVM-qfAO1dMkHTYCiGgECzRq1Xc0@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).