|
|
|
|
|
by mustache_kimono
888 days ago
|
|
Calm down. I note: "Here, you may be correct, that is less certain because the (FDK) license explicitly mentions needing to obtain a patent license." > By your broken rationale, if someone uses my free "AshamedSSL" library in a enterprisey security product and _their_ customers are hacked to no end, I'm liable. Citation needed. I'm not sure how this follows. How did they use your software? If licensed re: the MIT, you disclaimed liability already? What if your argument was closer to the facts: You license your software as MIT, you are aware of patent claims but are simply silent on the matter, and a user uses the software and is sued for patent infringement. If I were the licensee's attorney, I'd join you in the lawsuit arguing the good faith licensee relied on your apparent authority to convey the patent rights, and you induced my client to commit infringement by not disclosing patent claims which you were aware of. |
|
But anyway even with your constrained example this is not yet enough to claim inducement to commit infringement. You still need _intent_. None of the jurisprudence you quoted refers to a case where licensee != patent holder, much less one where licensee would not stand to benefit from your infringement, so I'm not even sure how are you going to build a case.
You would be opening yet another Pandora's Box since so far no one in the free software community would consider free/gratis redistribution of software-that-we-know-could-potentially-be-infringing (i.e. everything) as "induction to commit infringement". (Note that _selling_ such software has always been another story, with contributory infringement at least being on the table, and the reason RedHat, etc. have traditionally been so afraid of patents).