linux-kernel - Re: Laptop shock detection and harddisk protection

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] [day] [month] [year] [list]

Date:	Wed, 8 Oct 2008 01:03:59 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Greg KH <greg@...ah.com>
Cc:	Thomas Renninger <trenn@...e.de>, Tejun Heo <tj@...nel.org>,
	Shem Multinymous <multinymous@...il.com>,
	Elias Oltmanns <eo@...ensachen.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	IDE/ATA development list <linux-ide@...r.kernel.org>
Subject: Re: Laptop shock detection and harddisk protection

Hi!

> > > > Either I can take his sources on sourceforge.net (quite well known
> > > > place, right) as published information, or I could not use other well
> > > > known sources such as wikipedia.
> > > 
> > > If the wikipedia information was written based on these source files,
> > > no, we can't use that, sorry.
> > 
> > How do I know?
> 
> Unfortunatly, you can't, so don't use it.

Not being able to use wikipedia is little strong, don't you think so?
What's next?

> > This code is written by anonymous person. He may have used documents
> > improperly, but I see no signs of that, and don't see why I should
> > believe you saying so.
> > 
> > If have proof of that, you should talk to sourceforge to take that
> > code down... or probably their employer should ask sourceforge to do
> > that.
> > 
> > The documents are on the web from more than year now, on
> > well-known. That seems to indicate that your theory is not true.
> 
> Yes, I know this is true, for a variety of reasons of what people
> (including the individual in question) told me in private.

Are you saying Shem told you he violated some contracts?

Ok, so can you tell us the details, so that we can evaluate this
ourselves, and (more importantly) so that he can defend himself? He
seems willing to point where specific pieces of code come from.

> And I'm not going to go around asking for code to be taken down, as I'm
> not the one whose contract was invalidated.

Right. So why do you care if this code goes into kernel? Your contract
is not violated, and neither me nor you signed any contract preventing
us from putting that code into kernel.

If you know the details, can you tell us which/whose contract is being
violated here? Maybe we can just get permission of those parties. Or
maybe your information is wrong...

> Ok, once again:
>   - we know this code was created illegally.

If you know this, please share details.

> So can we please just drop this?  Or do you want me to point you at the
> lawyers?

I'll talk to lawyers if I have to. I'd like to understand this.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/