public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] CAcert certificate distribution license to third parties (i.e. distributors like gentoo)
Date: Mon, 14 Dec 2009 07:15:36 -0500	[thread overview]
Message-ID: <4B262C68.9030402@gentoo.org> (raw)
In-Reply-To: <robbat2-20091213T194815-557863620Z@orbis-terrarum.net>

On 12/13/2009 02:49 PM, Robin H. Johnson wrote:
> On Sun, Dec 13, 2009 at 10:44:05PM +1100, Daniel Black wrote:
>> Recently this got produced as a draft license for parties distributing
>> CAcert's root certificate(s) (like us).
>> https://svn.cacert.org/CAcert/Policies/Agreements/3PVDisclaimerAndLicence.html
> That's a pretty dense license. I can see why you had a headache.
>
> I believe that in it's current form, we will have to make sure we have a
> liability disclaimer to users for the license, but that should be about
> it.
>

First, I am not a lawyer.

The 3PV license does require that the user be presented with:
http://www.cacert.org/policy/NRPDisclaimerAndLicence.php

I'm not sure that simply posting the link in an einfo would satisfy the 
requirements.  We might need to post the full text to qualify as having 
presented it to the user - not sure about that.  I don't see anything in 
there that requires interaction though (hitting a yes button or anything 
like that).

The license itself is fairly short - we only need to post the NRP and 
not the 3PV license.  The 3PV is a license for Gentoo to distribute 
content to users under the NRP.  Users who don't redistribute the key 
don't need to worry about it.

An option would be to RESTRICT=mirror their root key, and install it 
directly from their site, assuming they don't start messing with the 
URL.  Then we can just put the license in the ebuild like any other. 
Since we don't redistribute anything copyrighted, Gentoo itself doesn't 
enter into any license agreement.

Only issue with that is that it is often bundled with a bunch of others 
and I don't know that you can restrict only one URL in the ebuild.



  reply	other threads:[~2009-12-14 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 11:44 [gentoo-dev] CAcert certificate distribution license to third parties (i.e. distributors like gentoo) Daniel Black
2009-12-13 19:49 ` Robin H. Johnson
2009-12-14 12:15   ` Richard Freeman [this message]
2009-12-14 20:10     ` Robin H. Johnson
2009-12-15  1:44       ` Richard Freeman
2009-12-15  6:46       ` Daniel Black
2009-12-15 12:19         ` Richard Freeman
2009-12-16 12:26           ` Daniel Black
2010-06-27  1:02 ` [gentoo-dev] " Daniel Black

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B262C68.9030402@gentoo.org \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox