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: <20250627000811.GB1598947@if>
Date: Fri, 27 Jun 2025 02:08:11 +0200
From: "Andries E. Brouwer" <aeb@....nl>
To: Alejandro Colomar <alx@...nel.org>
Cc: "Carlos O'Donell" <carlos@...hat.com>, "Andries E. Brouwer" <aeb@....nl>,
        linux-man@...r.kernel.org, linux-kernel@...r.kernel.org,
        libc-alpha@...rceware.org
Subject: Re: man-pages-6.14 released

On Fri, Jun 27, 2025 at 01:14:46AM +0200, Alejandro Colomar wrote:

> On Thu, Jun 26, 2025 at 07:01:24PM -0400, Carlos O'Donell wrote:

> > you need permission from the authors.
> > 
> > I disagree that man-pages should go forward with the current changes.
> > 
> > May you please restore the copyright notices and cut a new release?
> 
> Hmmm, it'll take some time.  I need to stop and compare the both lists,
> which are rather long.  I don't promise it will happen soon, but I'll
> keep it in a TODO list.  I'll also try to do it at least after
> September, when I'll be meeting Michael in person, where I'll ask him
> about his copyright notices (which represent a huge percentage of the
> copyright notice lines).  That will reduce the work significantly.
> So, it might happen around the end of this year.
> 
> Once I start doing that, I'll do another round of asking the remaining
> people about their copyright notices.  Hopefully, there'l l be few of
> them.


I think you are too sloppy.

Do you not recall the SCO saga?
There a big legal conflict arose over copyright ownership.
Something is still visible on https://en.wikipedia.org/wiki/SCO–Linux_disputes
Maybe this ancient matter has still not been completely settled.

Copyright is a legal matter, not something where convenience plays a role.
In principle you need permission of everyone involved, and not only that,
but you must be able to prove in court that everyone did give this permission.
So one needs written permission.
(And in what jurisdiction? Copyright details differ between countries.)
Some original copyright holders are no longer alive, and the rights
have been inherited.
Life is much easier if you regard those copyright sentences as fossils
carried over from earlier to later versions. And leave them verbatim.

Andries

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ