Providing a Closed Source License Upon Request?

goruka writes "As a citizen of the open source community, I have written several applications and libraries and released under the BSD license. Because of my license choice, I often run into the situation where a company wants to write software for a closed platform using my code or libraries. Even though there should be no restrictions on usage, companies very often request a different license, citing as a valid reason that the creator of such platform has special terms forbidding 'open source software' in the contracts forced upon the developer. So my question is, has anyone else run into this situation, and are there examples of such licenses that I can provide? (Please keep in mind that I'm not a US resident and I don't have access or resources to afford a lawyer there.)"

Re:Dual-license

[Anonymous Coward]

(1) Put backdoor in code if not there already. As if corporations would spend the time-money to look through it all.
(2) Offer them custom licensing for no less than six figures.
(3) ???*
(4) Profit.

* Freeze the code while in the negotiation process. If they pay the license, remove the backdoor. If they refuse the license, sell the exploit and wait for their servers to light up.

Re: Banning Open Source

[maxwell demon]

That's not so clear-cut. You obviously define "chicken-egg" as "egg from which a chicken grows" but "an egg laid by a chicken" is an equally valid definition. Indeed, one could even argue that it is a better definition, because for example from those chicken eggs you get in a supermarket in general there couldn't grow a chicken. Now applying that definition, the egg that your almost-chicken laid was clearly not a chicken egg, because it wasn't laid by a chicken. From this almost-chicken egg then grew a chicken, which subsequently laid chicken eggs. Therefore the chicken was first.

Of course all that ignores that there's no clear-cut line between chickens and non-chickens anyway.