bug#30619: Cuirass requires TLS certificates

[Maxime Devos]

zimoun schreef op wo 05-01-2022 om 00:09 [+0100]:
> 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. :-)

That suggestion (+ Ludovic's suggestion of a
(guix x509-certificates) module) was my suggested implementation, it
just needs to be translated from a description in English to an actual
patch .

Anyway, I don't think closing is reasonable, because the bug
(certificates need to be installed globally) still exist, and it
is actionable (there's even a suggested implementation,
so a sufficiently motivated party (not me currently) could address the
issue.

Greetings,
Maxime.

signature.asc
Description: This is a digitally signed message part