Slashdot Mirror
A Software License That's Libre But Not Gratis?
duncan bayne writes "My company is developing some software using Ruby. It's proprietary software — decidedly not free-as-in-beer — but I don't want to tie my customers down with the usual prohibitions on reverse engineering, modification, etc. After all, they're licensing the product from us, so I think they should be able to use it as they see fit. Does anyone know of an existing license that could be used in this case? Something that gives the customer the freedom to modify the product as they want, but prohibits them from creating derivative works, or redistributing it in any fashion?"
Like many people, you seem to assume incorrectly that copyright law, as defined historically, can be used to artificially control what people do with something they have received and use in their own privacy in the first place. You actually do not have to do anything outside of existing copyright law as it is historically understood and intended to accomplish what you desire. This is why the GNU General Public License, as a copyright license, has to explicitly offer the right to sub-license (distribute) original or derivative works.
Now some evil companies try to attach additional restrictions using common contract law to claim additional rights they do not actually have under copyright to deprive people of their existing and even constitutional rights (and what can in many situations be considered contracts of adhesion), and the results of these bastardizations are what is often called things like eula's.
um, like, hire a real lawyer. really, dude.
^ ^ That. Seriously. But secondly, You're asking about EULAs. The GPL is not a EULA. None of the libre/Open Source licenses are EULAs.
What you want is purely the domain of contract law. The conditions under which you license software you own are between you and the licensee. Plus whatever court has jurisdiction if either of you decides to sue. Hire a lawyer if you're not confident on what provisions are likely to hold up under a judges scrutiny.
You might want to check out Immunity.
http://www.immunitysec.com/
They sell CANVAS, an exploitation framework. A subscription is pretty expensive (that is, dirt cheap compared to core impact), but it comes complete with python source code, and the licence they use gives full rights to modify any of the code as you need to (sort of a requirement for exploit frameworks).
um, like, hire a real lawyer. really, dude.
That's real brilliant advice, but the problem is there are astonishingly few lawyers who will have the slightest clue how to answer this question.
I would suggest that a techie's best bet is to get as informed as possible before taking this to a lawyer, because it's really treading new ground. Can you tell I've been there?
Slim Devices, and subsequently Logitech, wanted to pursue this kind of license for our firmware, so that we could allow customers to have certain benefits of open source, without enabling competitors to make knock-offs of our hardware products with no effort beyond soldering down the parts.
Ages ago I came up with the Slim Devices Public Source License, which later got rolled into the Logitech Public Source License. Only recently did we actually ship a major firmware product based on it, which is the SqueezeOS platform that underlies the (imminently hackable, linux based) Squeezebox Controller. Customers can see the source code, learn how it works, customize it to their needs, etc, but they are not allow to redistribute without permission. It's not "Open Source" by the official definition, but it's a great compromise IMHO which met our business constraints.
I searched far and wide for lawyers who understood these technicalities, and even at a major multi-B corporation with an awesome legal team, this was new ground. So educate yourself and check out as many examples as possible, and then find a good IP specialist to help you craft a license, but be prepared to prescribe exactly what you want that license to do.
IANAL, but if you are not imposing a EULA, you shouldn't need any kind of license. End-user licenses restrict what can be done with the copy of the software that is owned. Licenses like the GPL restrict what can be done when redistributing the software, but impose nothing on the end-users. If you are not wanting to permit your end-users to redistribute, simple copyright is enough to protect your rights without the need for an additional licenseIf the software is not being redistributed and you aren't requiring a EULA, then the end-users are free to modify the software as they see fit (or do anything with it, except redistribute) under existing copyright law. So it seems copyright law as-is protects you from redistribution and permits your users the ability to modify the software, without the need of any license.
This is 100% incorrect. Copyright law does not allow some to create a derivative work without the consent of the copyright owner. And when I say derivative, I mean modification. The author of the summary is confused because he or she does not understand that a modification is a derivative work (assuming modification uses the original aspects of the work that the original author created himself.) You are assuming that copyright protects only from redistribution. That is wrong. Here is what the statute says:
15 USC 106. Exclusive rights in copyrighted works
Subject to sections 107 through 122, the owner of copyright under this title has the exclusive rights to do and to authorize any of the following:
(1) to reproduce the copyrighted work in copies or phonorecords;
(2) to prepare derivative works based upon the copyrighted work;
(3) to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending;
(4) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and motion pictures and other audiovisual works, to perform the copyrighted work publicly;
(5) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and pictorial, graphic, or sculptural works, including the individual images of a motion picture or other audiovisual work, to display the copyrighted work publicly; and
(6) in the case of sound recordings, to perform the copyrighted work publicly by means of a digital audio transmission.
http://www.copyright.gov/title17/92chap1.html#106
As you can see, derivative and distribution are two separate rights granted to the copyright holder.
> important to keep the source code super secret
The reason will most likely be listed below:
1. End users making their own changes but still complaining about error that may or may not be a result of their unauthorized modifications
2. Afraid that other competitors will 'leverage' your investment in development using legal or illegal means.
3. They don't want anyone to know that they 'leveraged' your investment in development to further their own product using legal or illegal means.
4. They didn't bother to patent anything and they're relying on being hidden to keep their trade secrets safe.
5. They license another developer's code which has the exact same limitation, and instead of negotiating with the upstream dev for source distribution rights or reimplementing the needed functionality themselves, they just choose to do nothing.
Anyways, many development environments/frameworks allow for source distribution because customers want to know why an obscure function 3 stack steps into your API routine is throwing ugly errors at you. With clear-and-open source, a developer could use a debugger and realize that they screwed something up before having to contact support with an obvious (to the original dev) problem.
Outside development libraries/frameworks and free products, a full source dump of any given product is pretty rare, at least from my experience.
Bye!
And this is why it's not a good idea to get legal advice on slashdot...
let's review:
The exclusive rights granted in copyright law are detailed in 17 USC S 106:
17 USC S 106 Subject to sections 107 through 122, the owner of copyright under this title has the exclusive rights to do and to authorize any of the following: ... (2) to prepare derivative works based upon the copyrighted work;
The statute uses the word prepare. You will be in violation even if you don't distribute your derivative work. For a case dealing with this specific subject, see Walt Disney Productions v Filmation Associates, at 628 F.Supp. 871. Unfortunately I can't seem to find a copy of it online.
IANAL
If you had super powers, would you use them for good, or for awesome?