Skip to contentSkip to conversation

use of patented algorithms in the kernel ok or not?

OT Albert Cahalan 11 participants 15 messages Dec 21, 2003 – Dec 22, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 9 lines · Linus
Quoted 3 lines · Lennert Buytenhek

What am I to do? Ignore the patent? Or should
I refrain from submitting the patch I wrote,
and look for an unencumbered algorithm instead?

Don't submit, and find an unencumbered algorithm.
Unless you can get the patent holder to grant a
license (it does happen).

What about the obvious Kconfig option?

config PATENT_1234567890
bool "Patent 1234567890"
default n
help
Say Y here if you have the right to use patent 1234567890 (the foo patent). Some countries do not recognise this patent, an educational or research exemption may apply, you may be the patent holder, the patent may have expired, or you may have aquired rights via licensing. Seek legal help if you need advice concerning your rights. If unsure, say N.

This assumes that the patented algorithm is important enough to bother with, and we'd all hope a non-patented alternative is available for those of us without rights to the patent.

#1 lore raw
Quoted 15 lines · Albert Cahalan

What about the obvious Kconfig option?

config PATENT_1234567890
bool "Patent 1234567890"
default n
help
Say Y here if you have the right to use patent 1234567890 (the foo patent). Some countries do not recognise this patent, an educational or research exemption may apply, you may be the patent holder, the patent may have expired, or you may have aquired rights via licensing. Seek legal help if you need advice concerning your rights. If unsure, say N.

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

1. You seggragate code using the feature so that if it is not explicitly activated, then the patented method will not be used.

2. You are clearly informing the recipient of the software of their need to determine for themselves whether they are permitted to use the feature, and suggest how they can go about this.

3. Using the patented method requires a clear, explicit step by the recipient of the software, with no potential for misunderstanding. It is just as clear as those disclaimer buttons, ensuring that a user knows their rights and duties and agrees to them before they are allowed access to something.

Closed source commercial software already does this sort of thing. Was it not the case that if you purchased the appropriate license from Unisys, you were then permitted to activate the GIF writing support of Photoshop or some similar product, and that was done with an activation code that you typed in to the program.

CONFIG_PATENT_nnnnnnnnn is the same thing, yet we are wary of distributing open source software like that. Is the significant difference that it's too easy to enable without a license? That may well prove to be the determining factor in clarifying the legal boundary of of who is liable - the sender of disabled code, or the recipient who enables it without permission.

Certainly it cannot be justified under law that, even as closed source implementations are distributed using activation code methods, the open source implementations are not distributable solely because they can be read by anyone. Patent holders do not have the power, at least not in law, to prevent sharing written explanations of a method, do they? I thought it had something to do with _using_ the methods, although it continues to be a bit ambiguous what a patent holder may restrict and what they have no legal right to restrict in this field.

-- Jamie

#2 lore raw
Quoted 17 lines · Jamie Lokier
Quoted 15 lines · Albert Cahalan

What about the obvious Kconfig option?

config PATENT_1234567890
bool "Patent 1234567890"
default n
help
Say Y here if you have the right to use patent 1234567890 (the foo patent). Some countries do not recognise this patent, an educational or research exemption may apply, you may be the patent holder, the patent may have expired, or you may have aquired rights via licensing. Seek legal help if you need advice concerning your rights. If unsure, say N.

Quoted 5 lines

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

This approach would turn Linux into proprietary software.

- James

Signature · 2 lines
James Morris
<[email protected]>
#3 lore raw
Quoted 1 line · James Morris

This approach would turn Linux into proprietary software.

You're saying a Linux kernel with _more_ capabilities that I and everyone else outside the USA can use, learn from, modify and distribute freely is proprietary, whereas denying me access to those capabilities is more free?

I guess it is more free for people living within the patented economic zones, and less free for people outside them.

To put it into perspective: I'd love for Mandrake or SuSE or Polish or Red Flag Linux to come with a full suite of modem, DSL and wireless drivers, and support for VFAT and Longhorn filesystems.

There's two ways to go about it:

1. First way is we develop a common Linux kernel which everyone in the USA may use, even if it contains things like encryption which are not so legal in some other parts of the world.

This is obviously how it's done right now.

Mandrake, SuSE, Polish, Red Flag and everyone else outside the USA must apply the Big Linux Patch to build kernels which support all the extra devices and filesystems.

2. Second way is to include all those extra wireless drivers etc. in the common kernel, but disable them somehow for USA users. Note that the USA users have not lost anything.

Distributing the code in disabled form _may_ not be legal in practice, I simply do not know, so maybe the second way is not permissible. But if there is a chance it is permissible, don't you think it should be explored?

-- Jamie

#4 lore raw
Quoted 3 lines · Jamie Lokier

2. Second way is to include all those extra wireless drivers etc. in the common kernel, but disable them somehow for USA users. Note that the USA users have not lost anything.

As long as no critical functionality is unaccessible to our American friends, I'd love that.

#5 lore raw
In reply to James Morris
Quoted 8 lines
Quoted 6 lines

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

This approach would turn Linux into proprietary software.

how so?
How is adding speed improvements to the code that may not be allowed in ONE country make linux proprietary? We can't just rip out each and every feature that ANY goverment or country in the world declares illegal/not allowed to be used. CONFIG_USA and the like only provide a hint/helper for those who want to use it in geographies where certain restrictions are imposed by law on what software is allowed to do (without paying third parties that is). Now of course it's a problem if the kernel wouldn't function at all with CONFIG_USA is set (although perfectly ok within the gpl afaics), but for additional performance improvements ?

#6 lore raw
Quoted 8 lines · Arjan van de Ven
Quoted 7 lines
Quoted 5 lines

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

This approach would turn Linux into proprietary software.

Quoted 10 lines

how so?
How is adding speed improvements to the code that may not be allowed in ONE country make linux proprietary? We can't just rip out each and every feature that ANY goverment or country in the world declares illegal/not allowed to be used. CONFIG_USA and the like only provide a hint/helper for those who want to use it in geographies where certain restrictions are imposed by law on what software is allowed to do (without paying third parties that is). Now of course it's a problem if the kernel wouldn't function at all with CONFIG_USA is set (although perfectly ok within the gpl afaics), but for additional performance improvements ?

What about the legal ramifications in the US of distributing code using an algorithm that is covered by a patent without permission. What are we gonna just not distribute the kernel in the US at all? Cause that's the only way to safely do what you all keep blathering about without a license. By putting the code in the kernel you are putting us in the US at risk, someone could argue you are giving people a means to violate a patent in the US...not something you want to be doing!

-sb

#7 lore raw
Quoted 9 lines · Stan Bubrouski

What about the legal ramifications in the US of distributing code using an algorithm that is covered by a patent without permission. What are we gonna just not distribute the kernel in the US at all? Cause that's the only way to safely do what you all keep blathering about without a license. By putting the code in the kernel you are putting us in the US at risk, someone could argue you are giving people a means to violate a patent in the US...not something you want to be doing!

Hard to say, but consider this:
Something patented is _not_ a secret, and therefore not a trade secret. Anything patented can be looked up in the patent databases by anybody. So there cannot be any problem with distributing this patented knowledge.

Using it is another matter, but it is up to the user not to disable CONFIG_USA within us jurisdiction.

Helge Hafting

#8 lore raw
In reply to Jamie Lokier
Quoted 17 lines · Jamie Lokier
Quoted 15 lines · Albert Cahalan

What about the obvious Kconfig option?

config PATENT_1234567890
bool "Patent 1234567890"
default n
help
Say Y here if you have the right to use patent 1234567890 (the foo patent). Some countries do not recognise this patent, an educational or research exemption may apply, you may be the patent holder, the patent may have expired, or you may have aquired rights via licensing. Seek legal help if you need advice concerning your rights. If unsure, say N.

Quoted 4 lines

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

<SNIP>

No No No No No...do you really think including code for a patented algorithm(s) is a good idea? You are still distributing the code and allowing people to illegally use it in countries where they are not allowed to. In essence you are providing a catalyst for them to violate a patent and making yourself and other liable along the way. US law is sick and fucked up, and if someone sues you for patent infringement you're most likely fucked, because you can never have enough money to defend yourself...for the sake of us stuck in this so-called free country (though we can be arrested and jailed without trial?) please do not include patented algoriths in Linux...

-sb

#9 lore raw
Quoted 24 lines · Stan Bubrouski
Quoted 21 lines · Jamie Lokier
Quoted 15 lines · Albert Cahalan

What about the obvious Kconfig option?

config PATENT_1234567890
bool "Patent 1234567890"
default n
help
Say Y here if you have the right to use patent 1234567890 (the foo patent). Some countries do not recognise this patent, an educational or research exemption may apply, you may be the patent holder, the patent may have expired, or you may have aquired rights via licensing. Seek legal help if you need advice concerning your rights. If unsure, say N.

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

<SNIP>

Quoted 10 lines

No No No No No...do you really think including code for a patented algorithm(s) is a good idea? You are still distributing the code and allowing people to illegally use it in countries where they are not allowed to. In essence you are providing a catalyst for them to violate a patent and making yourself and other liable along the way. US law is sick and fucked up, and if someone sues you for patent infringement you're most likely fucked, because you can never have enough money to defend yourself...for the sake of us stuck in this so-called free country (though we can be arrested and jailed without trial?) please do not include patented algoriths in Linux...

The question is "What toes are OK to step onto".

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)
(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!)

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.

Bis denn

Signature · 4 lines
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.
#10 lore raw
Quoted 2 lines · Matthias Schniedermeyer

The question is "What toes are OK to step onto".

I totally understand this. To a point.

Quoted 4 lines

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.

Quoted 4 lines

(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...

Quoted 4 lines

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

Quoted 5 lines

Bis denn

#12 lore raw
In reply to Stan Bubrouski
Quoted 10 lines · Stan Bubrouski
Quoted 4 lines

I expect this was said in jest, but it would be delightful to see this done for real. To the best of my knowlege it's uncharted territory, so perhaps what you suggest _would_ be upheld in a court of law as permissible?

No No No No No...do you really think including code for a patented algorithm(s) is a good idea? You are still distributing the code and allowing people to illegally use it in countries where they are not allowed to. In essence you are providing a catalyst for them to violate a patent and making yourself and other liable along the way.

That is equally true if I publish a book explaining the algorithm in great detail - enough detail that you could practically copy working code from the book. Yet, publishing books seems to be fine.

That's why I said it's uncharted territory. We don't know how safe it is to publish code that *doesn't do anything* but does embody a patented technique *only if the recipient deliberately modifies the code*.

Please explain the difference between publishing a book that doesn't do anything itself, but might "catalyse" a person to using a patented technique, and publishing source text that doesn't do anything, but might "catalyse" a person to using a patented technique *if they deliberately decide to infring the patent themselves*.

If anything, the book is more irresponsible because usually books don't tell the reader about patents on the methods they describe. On the other hand, we are very responsible and propose to tell the reader _exactly_ what their responsibilities are and the consequences of their actions if they choose to modify the work. We give them the knowledge and the choice.

Quoted 3 lines

US law is sick and fucked up, and if someone sues you for patent infringement you're most likely fucked, because you can never have enough money to defend yourself...

That's true. And they can sue you _even if you didn't do anything wrong_ and you're most likely fucked too. Innocence is no excuse.

So it has little to do with obeying the law, which is totally ambiguous in this area anyway, and a lot to do with being an undesirable target, doesn't it?

Quoted 2 lines

for the sake of us stuck in this so-called free country (though we can be arrested and jailed without trial?)

You can be arrested and jailed even if you _don't_ infringe any patents, too.

You have to be pragmatic, but if you are totally ruled by fear of what they _might_ do, you'll never do anything interesting. So we push the envelope a little bit and see how it works out. See if people find it acceptable practice, or if it's not a good time to encode that much personal freedom and responsibility.

It's not at all clear that !CONFIG_USA || CONFIG_PATENT_nnnnnnnnnn would be "illegal" in the USA. As you saw from the help text, there are many people and organisations _in the USA_ which would be permitted to enable the options.

It's a lot like the binary modules question, only this time it's the companies with patent portfolios that like to keep the status quo ambiguous, because it suits their position. We can recoil from the ambiguity, or we can take advantage of it to produce better software.

-- Jamie

#13 lore raw

Quote from Jamie Lokier <[email protected]>:

Quoted 4 lines

That's why I said it's uncharted territory. We don't know how safe it is to publish code that *doesn't do anything* but does embody a patented technique *only if the recipient deliberately modifies the code*.

Look at the MTD code.

John.

#14 lore raw
Quoted 8 lines · John Bradford

Quote from Jamie Lokier <[email protected]>:

Quoted 4 lines

That's why I said it's uncharted territory. We don't know how safe it is to publish code that *doesn't do anything* but does embody a patented technique *only if the recipient deliberately modifies the code*.

Look at the MTD code.

For examples of source code distribution in a patented area, look at MPEG4 projects, particularly MPEG4IP.

http://mpeg4ip.sourceforge.net/ has source code under a variety of licenses including GPL, and the front page has the following disclaimer:
"This code is not intended for end users, and does not contain executables. Please read all the legal information to determine if it is suitable for you."

The project was started by Cisco, who likely did some legal research first. Cisco, however, have the resources to see off frivolous lawsuits, while individual developers do not.

- Adrian Cox
http://www.humboldt.co.uk/