unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Libressl
Date: Mon, 15 Jun 2015 16:15:40 -0400	[thread overview]
Message-ID: <87eglciv83.fsf@netris.org> (raw)
In-Reply-To: <20150615191102.GA4777@debian> (Andreas Enge's message of "Mon, 15 Jun 2015 21:11:02 +0200")

Andreas Enge <andreas@enge.fr> writes:

> the attached patch adds libressl. As you can see, it is quite a bit simpler
> than the openssl package, which already inspires confidence. I think we
> should add the package;

Agreed.

> the next question would be whether we should switch
> all inputs from openssl to libressl. I tried it for fetchmail, and it works
> just the same.

I would be in favor of trying this in core-updates.  I have a lot more
confidence in the security of LibreSSL than OpenSSL.  The name
"LibreSSL" also better reflects the values of the free software
movement, which is a nice bonus.

> I also wonder whether we should not unite gnutls.scm and openssl.scm into
> one tls.scm.

Sounds good to me.

> +    ;; Files taken from OpenSSL keep their license, others are under various
> +    ;; non-copyleft licenses.
> +    (license (list license:openssl
> +                   (license:non-copyleft
> +                     "file://COPYING"
> +                     "See COPYING in the distribution.")))))

The COPYING file says that the OpenSSL code is under the OpenSSL license
and the new contributions are under ISC or public domain, so how about
this instead?

    (license (list license:openssl
                   license:isc)))))

   Thank you!
      Mark

  reply	other threads:[~2015-06-15 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 19:11 [PATCH] Libressl Andreas Enge
2015-06-15 20:15 ` Mark H Weaver [this message]
2015-06-15 20:30   ` Andreas Enge
2015-06-15 21:16     ` Mark H Weaver
2015-07-03 20:26       ` Andreas Enge
2015-06-16  9:56   ` Ludovic Courtès
2015-07-03 19:57   ` Andreas Enge
2015-07-05 15:17     ` Andreas Enge

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=87eglciv83.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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).