From: Kei Kebreau <kkebreau@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32530@debbugs.gnu.org
Subject: [bug#32530] [PATCH] gnu: octave: Fix CA certificate use.
Date: Thu, 13 Sep 2018 19:44:12 -0400 [thread overview]
Message-ID: <87h8it7yk3.fsf@posteo.net> (raw)
In-Reply-To: <87tvmtpz2r.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 13 Sep 2018 10:43:24 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Kei Kebreau <kkebreau@posteo.net> skribis:
>
>> * gnu/packages/maths.scm (octave)[arguments]: Add 'wrap-program' phase to wrap
>> Octave with the path to system CA certificates.
>
> [...]
>
>> + (add-after 'install 'wrap-program
>> + (lambda* (#:key outputs #:allow-other-keys)
>> + (let ((out (assoc-ref outputs "out")))
>> + (wrap-program (string-append out "/bin/octave")
>> + '("CURLOPT_CAPATH" suffix ("/etc/ssl/certs")))
>
> Users might want to ignore /etc/ssl/certs altogether and instead only
> use their own set of certificates, so I’m rather reluctant to such a
> change.
>
> Now, I agree that there’s a usability problem: we don’t want every
> Octave user to stumble upon a certificate error message. I can think of
> several solutions:
>
> 1. We could add CURLOPT_CAPATH to the ‘native-search-paths’ of ‘curl’,
> assuming that variable is honored by libcurl itself. It won’t
> solve this immediate issue, but it sounds like “the right way.”
>
> 2. On GuixSD, we could define CURLOPT_CAPATH=/etc/ssl/certs in
> /etc/profile, like we already do for other variables.
>
> 3. We could document this variable under “X.509 Certificates” in the
> manual.
>
> #1 would have to go to ‘core-updates’. WDYT?
>
> Thanks,
> Ludo’.
I don't mind putting #1 on 'core-updates' assuming it works. I will test
it locally first. Also, thanks for looking at this!
next prev parent reply other threads:[~2018-09-13 23:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 0:42 [bug#32530] [PATCH] gnu: octave: Fix CA certificate use Kei Kebreau
2018-09-13 8:43 ` Ludovic Courtès
2018-09-13 23:44 ` Kei Kebreau [this message]
2018-09-15 1:54 ` Kei Kebreau
2018-09-15 8:37 ` Marius Bakke
2018-09-15 18:30 ` Kei Kebreau
2018-09-17 16:33 ` Kei Kebreau
2018-09-17 17:16 ` Marius Bakke
2018-09-18 20:57 ` Kei Kebreau
2018-09-19 17:27 ` Marius Bakke
2018-09-19 19:52 ` Ludovic Courtès
2018-09-19 20:09 ` Marius Bakke
2018-09-19 20:18 ` Ludovic Courtès
2018-09-20 18:03 ` Kei Kebreau
2018-09-24 9:02 ` Ludovic Courtès
2018-09-25 1:43 ` bug#32530: " Kei Kebreau
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=87h8it7yk3.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=32530@debbugs.gnu.org \
--cc=ludo@gnu.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).