unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Openssl and certificate directory
Date: Sun, 8 Feb 2015 10:49:37 +0100	[thread overview]
Message-ID: <20150208094937.GA10816@debian> (raw)
In-Reply-To: <874mqx2mib.fsf@netris.org>

On Sat, Feb 07, 2015 at 08:57:32PM -0500, Mark H Weaver wrote:
> Unlike GnuTLS, OpenSSL supports setting the trust store location using
> environment variables, specifically SSL_CERT_DIR and SSL_CERT_FILE.
> Shouldn't we just use those?

I had read about these, but the documentation mentions them only in the
context of c_rehash. So I thought they were not generally applicable. But
indeed they are, I just tried SSL_CERT_DIR with youtube-dl. Also, it can be
a ":" separated list of directories. So we should probably encourage its
usage by defining a search path with our (future) certificate packages.

> If we were to apply this patch, I'd rather have just one rebuild rather
> than two, especially since our MIPS build slave is unable to keep up as
> it is.  What do you think?

So maybe we do not need it at all? What do you think? Concerning the rebuilds,
I would say that the aim of continuous integration would be to determine
exactly the place where something goes wrong, so in general, I am rather
in favour of more rebuilds. As the one mips machine cannot keep up, it would
then be reasonable to abort earlier builds.

Andreas

  reply	other threads:[~2015-02-08  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 15:17 Openssl and certificate directory Andreas Enge
2015-02-08  1:57 ` Mark H Weaver
2015-02-08  9:49   ` Andreas Enge [this message]
2015-02-08 14:22     ` Ludovic Courtès
2015-02-08 15:49       ` Mark H Weaver

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150208094937.GA10816@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).