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: <20090710133127.6839dc87@bike.lwn.net>
Date:	Fri, 10 Jul 2009 13:31:27 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Martin Steigerwald <Martin@...htvoll.de>
Cc:	David Newall <davidn@...idnewall.com>,
	Christoph Hellwig <hch@...radead.org>,
	Theodore Tso <tytso@....edu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	tridge@...ba.org, Jan Engelhardt <jengelh@...ozas.de>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Pavel Machek <pavel@....cz>, john.lanza@...ux.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>, jcm@...masters.org
Subject: Re: CONFIG_VFAT_FS_DUALNAMES regressions

On Fri, 10 Jul 2009 20:49:00 +0200
Martin Steigerwald <Martin@...htvoll.de> wrote:

> To me your thoughts appear to be *within* the patent approach and *thus* 
> implicitely saying "yes" software patents as such. Going this way I think 
> actually strengthen patents. 

One deals with reality on reality's terms.  For the moment, software
patents exist in some parts of the world.  People are working on that,
but one cannot just stick one's fingers into one's ears and wish the
problem away.

> The FAT patents have not yet been tested. 
> They might easily just be void and invalid.

The FAT patents *have* been tested, invalidated, and then revalidated.
Yes, they might still be invalid - I believe they are.  This helps a
Linux user whose products have been seized at the US border exactly
how? 

> But going the way you outline would be giving in to the patent claim 
> *before* it has even been tried and tested for validity. And thus IMHO 
> this strengthens the patent and it holder. If you change the upstream 
> kernel Microsoft can always say: "Look Linux kernel developers think that 
> the kernel infringed our patents." 

The point is not to give in to the claim; the point is to make it
irrelevant.  That "invalidates" the patent in a way which (1) doesn't
cost several million dollars and (2) is rather more certain in its
outcome.

> The linux kernel has not yet been proven to infringe any FAT patent. 
> Microsoft claims that it does. But so did SCO claim that it contains 
> source of UNIX that they said they have a license for. SCO could never 
> prove that claim. The linux kernel community ignored SCO for exactly that 
> reason. 

The Linux community did not ignore SCO.  We looked very hard at our
code and our processes, and adopted things like the DCO very much in
response to SCO.  The whole SCO affair has, IMO, made us a lot
stronger.

SCO is a very different story, though.  Copyright infringement is
usually pretty easy to avoid - just do your own work.  Patent
infringement happens regardless of how original your work is.

> Why on Earth should it handle Microsoft differently?  Just due to 
> its sheer size and weight in capital? The trial with TomTom just proves 
> nothing right now.

The TomTom trial proves that companies like TomTom have no real hope of
withstanding patent attacks and nicely invalidating obnoxious patents
as a favor for the rest of us.

Perhaps (a future version of) this patch isn't the right solution to
the VFAT patent problem.  Be we do need to figure out how we can
respond to patents which are being used to attack our users.  Telling
them to take the bullet and try to invalidate the patent for us isn't
going to fly.  Neither is ignoring the problem.

I have a lot of sympathy for Alan's assertion that we can't muck up our
upstream code with hackarounds for every bit of legal obnoxiousness we
encounter.  But outright refusal of things like patent workarounds does
not help us either.  Linux is a pragmatic system; somehow, I believe,
we can find a way to minimize our patent hassles without messing up the
system as a whole.

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