From: zimoun <zimon.toutoune@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
30619@debbugs.gnu.org, Andreas Enge <andreas@enge.fr>
Subject: bug#30619: Cuirass requires TLS certificates
Date: Wed, 05 Jan 2022 00:09:22 +0100 [thread overview]
Message-ID: <86r19nayjh.fsf@gmail.com> (raw)
In-Reply-To: <72886a55a3351fb56335c71179bdf155e27a630a.camel@telenet.be> (Maxime Devos's message of "Fri, 26 Nov 2021 06:28:20 +0000")
Hi Maxime.
On Fri, 26 Nov 2021 at 06:28, Maxime Devos <maximedevos@telenet.be> wrote:
> zimoun schreef op vr 26-11-2021 om 02:38 [+0100]:
>> On Fri, 15 Oct 2021 at 17:20, Ludovic Courtès <ludo@gnu.org> wrote:
>> > zimoun <zimon.toutoune@gmail.com> skribis:
>> > > On Thu, 16 Sep 2021 at 09:33, zimoun <zimon.toutoune@gmail.com>
>> > > > On Tue, 27 Feb 2018 at 17:00, ludo@gnu.org (Ludovic Courtès)
>>
>> > The Cuirass Shepherd service still does:
>> >
>> > #:environment-variables
>> > (list "GIT_SSL_CAINFO=/etc/ssl/certs/ca-
>> > certificates.crt" …)
>> >
>> > which means that users still need to install certificates globally.
>> >
>> > Now, whether it’s an issue, I don’t know.
>> >
>> > Maybe we can close?
>>
>> I propose to close since I do not see what could the next action.
>>
>> 1: <http://issues.guix.gnu.org/issue/30619>
>
> The next action would be splitting of the bundle generation from the
> profile code, and adding a ‘certificates’ field defaulting to nss-
> certs, as Ludo seemed to suggest.
Do you have an idea how to implement this suggestion? Otherwise, I
think closing is reasonable. :-)
Cheers,
simon
next prev parent reply other threads:[~2022-01-04 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 20:51 bug#30619: Cuirass requires TLS certificates Andreas Enge
2018-02-27 16:00 ` Ludovic Courtès
2021-09-16 7:33 ` zimoun
2021-10-12 21:57 ` zimoun
2021-10-15 15:20 ` Ludovic Courtès
2021-11-26 1:38 ` zimoun
2021-11-26 6:28 ` Maxime Devos
2021-11-26 6:31 ` Maxime Devos
2021-11-26 6:32 ` Maxime Devos
2022-01-04 23:09 ` zimoun [this message]
2022-01-05 9:53 ` Maxime Devos
2022-01-21 10:44 ` Maxime Devos
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=86r19nayjh.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=30619@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=maximedevos@telenet.be \
--cc=othacehe@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).