unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: openssl is now a dependency of guix: possible license conflict?
Date: Tue, 22 Aug 2017 10:32:46 +0200	[thread overview]
Message-ID: <87poboc89d.fsf@gnu.org> (raw)
In-Reply-To: <87a82wefmz.fsf@netris.org> (Mark H. Weaver's message of "Fri, 18 Aug 2017 17:21:24 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> Mark H Weaver <mhw@netris.org> writes:
>
>> There exist patches for libgit2 to support the mbedTLS library, but it
>> is not yet clear whether they will be accepted upstream:
>>
>>   https://github.com/libgit2/libgit2/pull/3462
>>   https://github.com/libgit2/libgit2/pull/3935
>
> Here's the currently-open pull request:
>
>   https://github.com/libgit2/libgit2/pull/4173
>
> I've attached work-in-progress patches to switch our libgit2 to use a
> modified version that supports mbedTLS.  Currently, there is a failing
> test in libgit2.  It may be a couple of days before I can work more on
> this.  I'm sending out these patches in case someone else wants to work
> more on this in the meantime.

Nice!

As Leo wrote, I think we should make sure that TLS support works
correctly, and in particular that authentication works (the
‘set-tls-certificate-locations!’ binding in Guile-Git.)

(I would also have a preference for GnuTLS over mbedTLS, if we had a
choice…)

Thanks for looking into this!

Ludo’.

      parent reply	other threads:[~2017-08-22  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  0:31 openssl is now a dependency of guix: possible license conflict? Alex Vong
2017-08-17  2:29 ` Mark H Weaver
2017-08-17  7:36   ` Mark H Weaver
2017-08-18 14:44     ` Alex Vong
2017-08-18 18:06       ` Leo Famulari
2017-08-18 21:21     ` Mark H Weaver
2017-08-19 12:51       ` Adonay Felipe Nogueira
2017-08-22  8:32       ` Ludovic Courtès [this message]

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=87poboc89d.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).