From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Help acme-client find its certificate store
Date: Wed, 14 Dec 2016 16:44:27 +0100 [thread overview]
Message-ID: <87inqma52c.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161214141944.GA7543@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Tue, Dec 13, 2016 at 05:15:05PM -0500, Leo Famulari wrote:
>> I'm successfully using this package with this change.
>>
>> I don't know if this is the "right way" to solve this. Your thoughts?
>
> To clarify, here is what happens on Debian Jessie without this change:
>
> $ acme-client -nN example.com
> acme-client: tls_config_set_ca_file: failed to open CA file '/etc/ssl/cert.pem': No such file or directory: No such file or directory
>
> And here are the upstream notes on this subject [0]:
>
> "You can also set DEFAULT_CA_FILE for the location of the certificate
> file loaded by libtls."
>
> https://github.com/kristapsdz/acme-client-portable/blob/master/README.md#configuration
>
>> + (let ((pem (string-append (assoc-ref inputs "libressl")
>> + "/etc/ssl/cert.pem")))
>> + (substitute* "http.c"
>> + (("/etc/ssl/cert.pem") pem))
>
> The upstream maintainer recommends setting this value in 'config.h', but
> it's only used in 'http.c', so I thought this solution would be a little
> easier to read.
LGTM. I did not know libressl maintains their own root trust.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2016-12-14 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 22:15 Help acme-client find its certificate store Leo Famulari
2016-12-14 14:19 ` Leo Famulari
2016-12-14 15:44 ` Marius Bakke [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=87inqma52c.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.