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: <m3642pl32w.fsf@maximus.localdomain>
Date:	Wed, 05 Sep 2007 14:16:39 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Daniel Hazelton <dhazelton@...er.net>
Cc:	davids@...master.com,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: That whole "Linux stealing our code" thing

Daniel Hazelton <dhazelton@...er.net> writes:

>> Actually (and I think it's the same in the USA), a copyrighted work
>> has an implicit "all rights reserved". A licence is just exception.
>
> And? The fact remains that "All Rights Reserved" means "I am reserving all 
> rights I do not specifically grant or waive".

Sure.
That means you can't use a work without obtaining a licence first
(unless you are the copyright holder and don't need (can't have)
the licence).

I.e., as the author, you don't have to write those "copyright xxx"
and the work is still protected.

> ie: If a license doesn't 
> state 'The licenser hereby waives the right to revoke this license at any 
> time' then that right hasn't been lost.

Yes, it hasn't been *lost*. It just never existed :-)
(with exception of those things starting 40 or so years after the
original publication, I think we can safely skip this part).

Obviously, the copyright holder is free to distribute the work
under a different licence next time (but (s)he has to make sure it's
ok with licences (s)he uses, if it's a derived work).
-- 
Krzysztof Halasa
-
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