lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1011091042120.28359@asgard.lang.hm>
Date:	Tue, 9 Nov 2010 10:42:41 -0800 (PST)
From:	david@...g.hm
To:	Elvis Dowson <elvis.dowson@....com>
cc:	Greg KH <greg@...ah.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline

On Tue, 9 Nov 2010, Elvis Dowson wrote:

> Hi Greg,
>
> On Nov 9, 2010, at 10:24 PM, Greg KH wrote:
>
>> If you have the rights to make the changes to the andoid userspace code,
>> great.  Otherwise you are not going to get very far.
>
> Isn't the whole Android stack licensed under Apache 2.0? Doesn't everyone
> have full access to the android userspace code?
>
> In your slides, you made several references to only google developers being
> able to modify the low-level libraries, which I admit I still don't understand.
>
> If we have full access to the source under an Apache 2.0 license, what would
> prevent us from making the required modifications and re-releasing the
> modified sources under the same Apache 2.0 license?

you can modify them, but unless those modifications get used, what good 
are they?

David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ