#49508 Implement --allow-insecure-transport for `guix pull`

Message #5 received at submit@debbugs.gnu.org (full text, mbox, reply):

From: Leo Famulari <leo@famulari.name>

To: bug-guix@gnu.org

Subject: Implement --allow-insecure-transport for `guix pull`

Date: Sat, 10 Jul 2021 13:28:10 -0400

As discussed in #46829, `guix pull` needs an option like
--allow-insecure-transport so that users can continue to pull from the
same channel even when their local certificate store has expired or is
otherwise invalid.

[0] <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46829#114>

Message #10 received at 49508@debbugs.gnu.org (full text, mbox, reply):

From: Ludovic Courtès <ludo@gnu.org>

To: Leo Famulari <leo@famulari.name>

Cc: 49508@debbugs.gnu.org

Subject: Re: bug#49508: Implement --allow-insecure-transport for `guix pull`

Date: Tue, 08 Feb 2022 11:18:08 +0100

Hi,

Leo Famulari <leo@famulari.name> skribis:

> As discussed in #46829, `guix pull` needs an option like
> --allow-insecure-transport so that users can continue to pull from the
> same channel even when their local certificate store has expired or is
> otherwise invalid.

Agreed.

Unfortunately it seems that libgit2 doesn’t let us turn off certificate
verification:

  https://libgit2.org/libgit2/#HEAD/group/libgit2

‘verify_server_cert’ in src/streams/openssl.c is called
unconditionally.  So it seems that the first thing to do would be to
submit a patch upstream that would allow users to disable certificate
checks via ‘git_libgit2_opts’.

Now, by default, ‘guix pull’ honors /etc/ssl/certs.  Assuming those are
up-to-date, it should be fine, right?

Thanks,
Ludo’.

Message #15 received at 49508@debbugs.gnu.org (full text, mbox, reply):

From: Leo Famulari <leo@famulari.name>

To: Ludovic Courtès <ludo@gnu.org>

Cc: 49508@debbugs.gnu.org

Subject: Re: bug#49508: Implement --allow-insecure-transport for `guix pull`

Date: Tue, 8 Feb 2022 12:11:32 -0500

On Tue, Feb 08, 2022 at 11:18:08AM +0100, Ludovic Courtès wrote:
> Unfortunately it seems that libgit2 doesn’t let us turn off certificate
> verification:
> 
>   https://libgit2.org/libgit2/#HEAD/group/libgit2
> 
> ‘verify_server_cert’ in src/streams/openssl.c is called
> unconditionally.

Ah, that's not surprising.

> So it seems that the first thing to do would be to
> submit a patch upstream that would allow users to disable certificate
> checks via ‘git_libgit2_opts’.

Right, but it might not be accepted.

> Now, by default, ‘guix pull’ honors /etc/ssl/certs.  Assuming those are
> up-to-date, it should be fine, right?

Yeah, I think so.

Message #18 received at 49508@debbugs.gnu.org (full text, mbox, reply):

From: Mathieu Othacehe <othacehe@gnu.org>

To: Ludovic Courtès <ludo@gnu.org>

Cc: 49508@debbugs.gnu.org, Leo Famulari <leo@famulari.name>

Subject: Re: bug#49508: Implement --allow-insecure-transport for `guix pull`

Date: Tue, 01 Nov 2022 18:30:52 +0100

Hello,

> ‘verify_server_cert’ in src/streams/openssl.c is called
> unconditionally.  So it seems that the first thing to do would be to
> submit a patch upstream that would allow users to disable certificate
> checks via ‘git_libgit2_opts’.

While this seems like something that we definitely want, I think we
shouldn't block the release with a contribution that can take time to be
upstreamed in libgit2.

Unblocking #53214.

Mathieu

Send a report that this bug log contains spam.