Do warranty disclaimers in software licenses carry any legal weight? Most open source software licenses contain, in capital letters, the following disclaimer: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Does such a disclaimer carry any legal weight? That is, if my license doesn't contain such a clause, can I as a distributor of the software be held liable for damages, and if it does contain such a clause, does it effectively prevent me for being held liable?
Some jurisdictions provide for statutory warranties on fitness and merchantability of goods. The effect of these exclusion clauses will vary between jurisdictions, so I will briefly examine two different effects of law with respect to supply of goods. For the United States, certain warranties are implied in the sale of a product, provided for in the Uniform Commercial Code § 2-314, (1) Unless excluded or modified (Section 2-316), a warranty that the goods shall be merchantable is implied in a contract for their sale if the seller is a merchantwith respect to goods of that kind. Under this section the serving for value of food or drink to be consumed either on the premises or elsewhere is a sale. (2) Goods to be merchantable must be at least such as (a) pass without objection in the trade under the contract description; and (b) in the case of fungible goods, are of fair average quality within the description; and (c) are fit for the ordinary purposes for which such goods are used; and (d) run, within the variations permitted by the agreement, of even kind, quality and quantity within each unit and among all units involved; and (e) are adequately contained, packaged, and labeled as the agreement may require; and (f) conform to the promise or affirmations of fact made on the container or label if any. (3) Unless excluded or modified (Section 2-316) other implied warranties may arise from course of dealing or usage of trade. The Uniform Commercial Code § 2-315 states that: Where the seller at the time of contracting has reason to know any particular purpose for which the goods are required and that the buyer is relying on the seller's skill or judgment to select or furnish suitable goods, there is unless excluded or modified under the next section an implied warranty that the goods shall be fit for such purpose. This means that the warranties in § 2-314 will generally apply to products that are sold, unless excluded as per § 2-316 UCC § 2-316 (2) Subject to subsection (3), to exclude or modify the implied warranty of merchantability or any part of it the language must mention merchantability and in case of a writing must be conspicuous, and to exclude or modify any implied warranty of fitness the exclusion must be by a writing and conspicuous. Licenses that specifically exclude implied warranty are sanctioned by the UCC, and therefore would be considered in the United States. UCC §2-106 defines a sale as passing of title from the seller to the buyer for a price. States may have additional laws that may affect the interpretation of the UCC. For example, Ark.Code Ann. § 4–1–201(32): (29) "Purchase" means taking by sale, lease, discount, negotiation, mortgage, pledge, lien, security interest, issue or reissue, gift, or any other voluntary transaction creating an interest in property. However, Neuhoff v. Marvin Lumber and Cedar Co., 370 F.3d 197 (1st Cir.2004) held that windows provided free of charge to replace defective windows did not come with implied warranty. However, not all jurisdictions allow the exclusion of implied warranty. For instance, consider Australian Consumer Law. (Part 3-2, Division 1): 54 Guarantee as to acceptable quality (1) If: (a) a person supplies, in trade or commerce, goods to a consumer; and (b) the supply does not occur by way of sale by auction; there is a guarantee that the goods are of acceptable quality. (2) Goods are of acceptable quality if they are as: (a) fit for all the purposes for which goods of that kind are commonly supplied; and (b) acceptable in appearance and finish; and (c) free from defects; and (d) safe; and (e) durable; as a reasonable consumer fully acquainted with the state and condition of the goods (including any hidden defects of the goods), would regard as acceptable having regard to the matters in subsection (3). 64 Guarantees not to be excluded etc. by contract (1) A term of a contract (including a term that is not set out in the contract but is incorporated in the contract by another term of the contract) is void to the extent that the term purports to exclude, restrict or modify, or has the effect of excluding, restricting or modifying: (a) the application of all or any of the provisions of this Division; or (b) the exercise of a right conferred by such a provision; or (c) any liability of a person for a failure to comply with a guarantee that applies under this Division to a supply of goods or services. (2) A term of a contract is not taken, for the purposes of this section, to exclude, restrict or modify the application of a provision of this Division unless the term does so expressly or is inconsistent with the provision. 67 Conflict of laws If: (a) the proper law of a contract for the supply of goods or services to a consumer would be the law of any part of Australia but for a term of the contract that provides otherwise; or (b) a contract for the supply of goods or services to a consumer contains a term that purports to substitute, or has the effect of substituting, the following provisions for all or any of the provisions of this Division: (i) the provisions of the law of a country other than Australia; (ii) the provisions of the law of a State or a Territory; the provisions of this Division apply in relation to the supply under the contract despite that term. What the above sections mean : (54) there are implied statutory warranties (64) that cannot be excluded by contract, (67) and applies even if the proper law of a contract is not Australia. It is important to note that these do not depend on the existence of a contract (see 54(1)); gifts are covered, though I am unaware of any case law on this. In addition, title (s51) and non-infringement ("undisturbed possession") (s52) must be guaranteed by the supplier and cannot be excluded. In addition, the mere existence of this statement, purporting to limit or remove guarantees that cannot be limited or excluded, puts the supplier in breach of s29 as they are making a "false or misleading statement in connection with the supply, possible supply or promotion of goods or services". This is a criminal or civil offence and can be punished by fines of up to $1.1 million for a body corporate and $220,000 for a person other than a body corporate plus injunctions, damages, compensatory orders and other remedies. However, a simple "To the extent permitted by law ..." at the start would make this legal. So, does it have an effect? Sometimes. But not always. And at least in the United States, there are specific requirements if you want to exclude implied/statutory warranty.
The exact laws will vary by region and country, but the laws will range anywhere between illegal and almost illegal. If you want to operate as legal as possible then you will have to disclose to the buyer that the software is malware or a crypter and you should require for the buyer to sign an agreement to only use the software for legal and educational purposes. Hiding the disclosure in a long Terms of Service agreement will likely not be sufficient. You will have to explicitly advertise that the software is malware and a crypter and that you are looking for reputable tech firms to buy your software in order to improve their software. If you sell software without disclosing to the customer that the software contains malware or a crypter then you are exposing yourself to a lawsuit for products liability, invasion of privacy, fraud and misrepresentation, the cost of damages, and possibly criminal liability.
Can the name of my LLC include the phrases "Software Engineer", "Software Engineering", or similar derivations thereof? No. Not based on what you've posted. Go to the definitions to see how engineer is defined. It may be they are talking about actual structural engineers or environmental engineers, where if you're wrong people die. But based on above, you can't use the word engineer unless you're licensed as such. Is there even a license for computer engineer? This seems more like it could be a term of use but not actually descriptive of what you're doing. IDK. You'd have to see the definitions and exceptions. Can my resume, curriculum vitae, or my advertising or promotional materials accurately report the subjects I studied in college as the subject matter of "Software Engineering", to the extent that this information is true and accurate? Yes, your CV is supposed to say what you have done, and learned and especially published (lest it's just a resume), but the answer as far as promotional materials, is NO. This, because you don't post your cv on your ad's and if you put that, you will likely be found to be trying to pose as a licensed professional based on a technicality. If that happens the licensing authority will probably censure you by disallowing a license when your qualify. If asked directly by a client, am I even allowed to divulge my area of study accurately,(of course, but you'd also have to divulge the fact that you are not licensed and cannot act in that capacity) Would it be a violation of the law to claim I had engineering knowledge since I have studied (and practiced) software engineering in the past (for instance, at previous places of work in states which did not have these kinds of limitations, or for corporations which did not offer my services to the general public)? It could be if the person reports that you are soliciting work as an engineer w/out a license. It's like a person who went to law school, passed the bar, but never got sworn in. They cannot solicit business as a lawyer. Unless there is a license for being a computer programer, there is nothing barring you from using that terminology. You could be, that if you look up the definition prior to the statue, that it says something like "for the purposes of this section the term engineer means…", In which case it doesn't even apply to you.
Gather evidence that the software you are requesting the source code of really is based on, in whole or part, an existing open source project that has a license which requires source code to be made available, and then contact that projects copyright holders. Only they have standing to sue.
Can you locate your license (generally not a trivial task)? It may appear under Help-About and a click to view EULA. The EULA specifically addresses redistribution of parts of the software and number of installations you can make with a single license. They do not say what uses you make make of the software, except that &quot;You may not rent, lease, lend or provide commercial hosting services with the Software&quot;. There is no express prohibition against commercial or non-commercial political use of the product: anything not prohibited is allowed. The fact that they say nothing about the content that you create with Word means, they have declined to have a say in the matter. (I am not sure about the wording of the &quot;Educational&quot; versions of Office: those are somewhat negotiated between the institution and MS).
Yes. This is a frequently asked question on the foundation's homepage, and answered without ambiguity (source): Can I use a Raspberry Pi in a commercial product? This is a very common question, and the answer is yes! Once you have bought a Raspberry Pi, it's yours to do with as you wish. You would be in good company too, as in fact the Raspberry Pi is regularly used and sold for commercial applications third parties. Note that this the default consequence of a contract of sale in all jurisdiction I know of (but I am not a lawyer): The seller does not retain property rights in the particular item, and by the mere selling of the item implies there are no other rights that might prevent the buyer from using it as they wish. Apart from the particular computer now in your property, there are other legal requirements: &quot;Copyleft&quot; softweare: Large parts of the Raspbian software are licensed under &quot;copyleft&quot; licenses (importantly, versions of the General Public License, GPL). These licenses are meant to provide your customers with the means of reproduciing and building upon the &quot;copylefted&quot; software. You will need to provide your customers with the source code to those software items, the tools and documentation needed for building, and a written notice. Your own programs need not be licensed under a &quot;copyleft&quot; license, provided that you don't build on (distribute &quot;derative works&quot; of) &quot;copyleft&quot; software. The open source licenses involved are not meant to exclude commercial use, and there are helpful compliance guides available ( a, b ). Non-free software: Make sure to not include non-free software, like Mathematica or Oracle Java, which are not licensed for commercial redistribution. Trademarks: Your use of the words &quot;Raspberry PI&quot; or the raspberry logo is subject to restrictions, as is usual with trademarks. Speaking of the logos: You can request permission to use their &quot;powered by Raspberry Pi&quot; logo. Market regulations: You need to abide by regulations, for example safety and electromagnetic interference. Repackaging the Pi might mean you'll need to test and recertify your product, I'm not an expert. Video codecs: Some Raspberry Pis (up to 3) include specialised video decoding hardware. If you want to use it with the MPEG2 codec, you'll have to buy an activation key for small one-time fee per device - £2.40 for MPEG2, £1.20 for VC-1; other codecs are already activated. I don't think you'll need a license even for commercial, for-sale devices, but I am not your lawyer. Just to be clear, nothing prevents your buyers from cloning your software. (This is not a consequence of you providing the Raspbian source code - they can just clone the contents of your SD card.) While you can retain copyright in your own code, you'll probably have no effective means of detecting infringement. However, the physical design of the rest of your device will not be affected. Your business model needs to account for this fact.
Can anybody create their own license? That is to say, can I for example create my own license under which I can license software? Yep. It's just a contract granting rights to use a copyrighted work. You can write your own contracts, so you can write your own software license. It's just often recommended that you don't, because common licenses are more well-understood, and inexperienced drafters may make errors that could result in problems, such as unintended restrictions, failing to restrict things that were intended to be restricted, or creating provisions that aren't enforceable in some/all jurisdictions. Can you mandate how a software will be released? Yes. Many software licenses, including GPL, do. The restrictions you describe in your example sound similar to CC BY-NC-SA. Also, would the following clause even be legal? Using this software you agree that any work and intellectual property based on or created with this software will be under the [INSERT_NAME_LICENSE] license, even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up I'm not entirely certain, but &quot;even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up&quot; seems, in my opinion, unlikely to be enforceable—especially &quot;even if the work is rebuilt from the ground up.&quot; How would you differentiate a complete rebuild from a totally new piece of software? More broadly, once your copyrighted code is no longer in the product, there's nothing for them to license from you. It's hard to imagine how you'd be able to claim that you're harmed by someone releasing a new version of a product that used to contain your code under a different license. Without harm to you, there's nothing for a court to redress.
it would violate law? It would be very dependent of what your jurisdiction is and what the software does. I would expect most software that would be lawful to install at your home would be lawful to install at your company, but there may be exceptions. To put an hyperbolic example, if you work at the CIA and you install some remote access software that allows you to access your workstation from a non-secure PC through non-secure methods, I am pretty sure that would be illegal, even if you had the best of intentions. A recent scenario taken from real life involves some members an organization who are required to use official e-mail servers for FOIA purposes setting up their own private mail servers. Of course, YMMV. can I purchase it for myself, and then use at workplace Even if the software is legal it does not mean that it is ok to use it at the workplace. Most business have rules about what software may be installed in the PCs, who may install it and how to manage it. Your software could introduce security vulnerabilities that your IT team may need to be aware of, or incompatibilities with other software. It may introduce legal liabilities (you install a "home edition" licence in a corporate environment where that licence is invalid). Your company may discipline you if you breaking those guidelines and install software without authorization, even if there is no harm for them for this action. On top of that, if your actions cause some damage to the company, it can sue you to get you to pay for those damages. Before taking any action you should inquiry about your company's IT policy and, if your company does not have one or if the policy is not clear about allowing you to install the software, ask the people in charge (preferably in writting).