mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stan Bubrouski <stan@ccs.neu.edu>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [OT] use of patented algorithms in the kernel ok or not?
Date: Sun, 21 Dec 2003 15:11:14 -0500	[thread overview]
Message-ID: <1072037473.1286.132.camel@duergar> (raw)
In-Reply-To: <20031221195528.GA29261@citd.de>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

On Sun, 2003-12-21 at 14:55, Matthias Schniedermeyer wrote:
> The question is "What toes are OK to step onto".
> 

I totally understand this.  To a point.

> e.g.
> To the best of my knowledge it should be illegal to distribute 2.6
> kernel in France because AFAIK it is illegal to use encryption there.
> (If not France, there are other countries that fit)

True, but that has always been the case.

> (And you remember that this same problem was only resolved a few years
> ago for the U.S.! Otherwise the crypto-stuff would have been in kernel
> for years!)
> 

This really isn't a crypto question though, and this has financial
ramifications here as well.  Violating a French law isn't as scary to me
as having to hire a patent lawyer here in the US...

> So the only question is "Is it OK to step on the U.S. toe?".
> I guess there are other countries on this small planet (>200 IIRC) where
> the current linux kernel has it's "problems(tm)" here and there.
> 

Hey I'm all for allowing the use of patented algorithms in the kernel,
but I think they should be separate trees or patches that can be applied
and hosted elsewhere, the same way crypto was afor a long time.  I think
the idea should be to step on as few toes as possible, not knowingly do
it because it can be done...that's all.  You have to remember, patents
here are frightening, and you damned well better have a lot of money if
you are going to need a patent lawyer, that is a commodity most of us
can't afford.

-sb

> 
> 
> 
> 
> Bis denn

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-21 20:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21  1:12 Albert Cahalan
2003-12-21 10:53 ` Jamie Lokier
2003-12-21 13:35   ` James Morris
2003-12-21 14:30     ` Jamie Lokier
2003-12-21 16:03       ` Xavier Bestel
2003-12-21 14:56     ` Arjan van de Ven
2003-12-21 19:33       ` Stan Bubrouski
2003-12-21 23:25         ` Helge Hafting
2003-12-21 19:29   ` Stan Bubrouski
2003-12-21 19:55     ` Matthias Schniedermeyer
2003-12-21 20:11       ` Stan Bubrouski [this message]
2003-12-21 21:52       ` Francois Romieu
2003-12-21 21:57     ` Jamie Lokier
2003-12-22  9:50       ` John Bradford
2003-12-22 15:34         ` Adrian Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-12-22  1:43 James Lamanna
2003-12-22 11:32 ` Matti Aarnio
2003-12-18 23:11 Lennert Buytenhek
2003-12-19  6:10 ` Linus Torvalds
2003-12-19  7:38 ` Paul Jackson
2003-12-19  8:47 ` Arjan van de Ven
2003-12-19 11:38   ` Jan-Benedict Glaw
2003-12-20 17:28   ` Stefan Traby
2003-12-21 10:33   ` Jamie Lokier
2003-12-21 16:57     ` Pavel Machek
2004-01-13 15:35       ` Chuck Campbell
2004-01-13 19:35         ` Pavel Machek
2004-01-13 21:04           ` Richard B. Johnson
2003-12-22  0:37     ` jw schultz
2003-12-21 23:39   ` Lennert Buytenhek
2003-12-21  1:25 ` jw schultz
2003-12-21 19:40   ` Lennert Buytenhek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1072037473.1286.132.camel@duergar \
    --to=stan@ccs.neu.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®