linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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]

Date:	Sat, 16 Jun 2007 10:12:50 +0800
From:	Tim Post <tim.post@...kinetics.net>
To:	Scott Preece <sepreece@...il.com>
Cc:	Alexandre Oliva <aoliva@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Rob Landley <rob@...dley.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Fri, 2007-06-15 at 19:52 -0500, Scott Preece wrote:

> 
> Yes, but in highlighting the possibility of evil intentions you
> distort the fact that usually there are no such evil intentions...
> 

I don't think you can use "usually" and "fact" together like that. Why
is it so bad to account for them since they (do) surface and (could)
increase significantly in frequency? 

For me, the (could) is enough to act upon, regardless of the current
likely hood of it happening. Things change frequently. 

This, unfortunately comes pre-distorted depending on what you believe.
All of us are right but we still don't agree. Quite a fluke. 

That's the problem.

Best,
--Tim



-
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/