Is it legal to lend out your computer with licensed software installed on it? A company in Europe has temporarily given some of its computers with licensed Microsoft Visual Studio 2010 Premium to a company in Asia. The European company is the client of the Asian company and the software is used for developing a web application for the client. Microsoft now insists the Asian company is making unauthorized use of the licensed software because the licenses are country specific and geographically limited. Microsoft now demands a separate purchase of the licenses by the Asian company; just uninstalling isn't good enough. This will cost $5999 per user. Can licenses really be this limiting? I edited my old question, because it was seeking specific legal advice. I hope its fine now.
The companies really need to speak to an IP lawyer as this question is seeking specific advice which this site is loathe to give out for fear of compouding issues. The answer would depend on the license agreements and enforceability in various jurisdictions. According to https://social.msdn.microsoft.com/Forums/vstudio/en-US/0368d7ee-0eb3-4e3e-a143-4410969a15bb/eula-for-vs2010?forum=vssetup Microsoft says you cant rent out the software - but this applies to the "Pro" version - I could not find anything on the "Premium" version - so most likely Microsoft to have some clam. The flipside is how enforceable this EULA is - and this would probably vary from jurisdiction to jurisdiction. It would be a very, very good idea to speak to a lawyer before letting Microsoft come onto the premises - as "inviting them" to do this is almost certainly not going to improve the Asians company's case and will allow Microsoft to go fishing further and make it easier for them to expand on and collect evidence should they decide to pursue the matter.
Generally, such sanctions prevent certain sorts of transactions in goods and services with nationals or entities of the nation under sanction. The exact list of transactions prohibited or restricted varies. If Open source software were being provided as a service, so that the recipient paid directly for a license, or for customization or configuration work, or for some sort of consulting or assistance, such transactions could be banned or restricted by a sanctions regime, but might not be. (If the sanctions included that particular class of transactions.) However, if it is merely a matter of an open source product being published, for anyone to download, install, and use, I don't see how that would be barred or restricted by any sanctions of the sort recently in use.
If you aren't including those libraries, then yes because it's entirely your own work. If you are publishing those libraries, then no because their licenses will limit how you can do that. GPL's and MIT's main features are restricting how you can distribute software that includes the licensed code, and they don't allow the &quot;do whatever you want&quot; of public domain.
The starting point is whether you infringe copyright by downloading or using the cracked software. The licence you purchase relates to a specific copy of the software. The licence almost certainly does not say 'You can use any copy of this software.' It will usually say something like 'You may install this software', surrounded by other language that makes it clear that 'software' refers to a specific copy. E.g. the Windows 7 EULA says 'you may install one copy of the software on one computer' and, in another place, says 'By using the software, you accept these terms. If you do not accept them, do not use the software. Instead, return it to the retailer for a refund or credit.' Nothing in that licence allows you to download an infringing copy of Windows from elsewhere and apply your licence to that copy. In the case of Windows, you don't have a licence to run 'Windows', you have a licence to run a specific copy of Windows. Therefore, even though you have purchased a licence, you would not have a licence for the cracked copy. Running a computer program inherently requires you to make copies of it in memory. In the absence of a copyright licence, this is copyright infringement: MAI Systems Corp v. Peak Computer Inc (1993) 991 F.2d 511 (defendant, who was not a licensee in relation to software, ran software and in doing so created copies of the software in memory; the person was purportedly authorised by a licensee to do so, but the licensee did not have the right to so authorise the defendant). In some jurisdictions, there is legislation to permit non-licensees to run software without infringing copyright, but these provisions (at least the ones in the US and Australia) don't apply to copies of the program which are themselves infringing copies. See 17 USC 117(a) and section 47B of the Copyright Act 1968 (Cth). Now, supposing you do infringe copyright, the question of whether that is a criminal act will depend on the jurisdiction and the other facts of the case. In Australia, downloading or using software is almost never a criminal act (offences under the Copyright Act require trade in infringing copies or commercial scale, etc). In the US, infringing copyright for commercial gain (e.g. if the software is for use in a business) or of particularly expensive software might be criminal under the No Electronic Theft Act. Furthermore, downloading the 'cracked' software may make one complicit in the distributor's offending, specifically by way of 'counselling and procuring' or 'conspiracy'. The distributor's offending may include the kind of commercial copyright infringement that is criminalised.
Only if you ask Valve for permission first, and they agree in writing. I'm not a lawyer, but when I was reading through the Subscriber license you linked, this stuck out to me: You are entitled to use the Content and Services for your own personal use, but you are not entitled to: (i) sell, grant a security interest in or transfer reproductions of the Content and Services to other parties in any way, nor to rent, lease or license the Content and Services to others without the prior written consent of Valve, except to the extent expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use); (ii) host or provide matchmaking services for the Content and Services or emulate or redirect the communication protocols used by Valve in any network feature of the Content and Services, through protocol emulation, tunneling, modifying or adding components to the Content and Services, use of a utility program or any other techniques now known or hereafter developed, for any purpose including, but not limited to network play over the Internet, network play utilizing commercial or non-commercial gaming networks or as part of content aggregation networks, websites or services, without the prior written consent of Valve; or (iii) exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use). The part that I've bolded is probably the part that makes this against the Terms of Service, since in order to post these sorts of automated messages to their service, you'd need to use a &quot;utility program&quot; to &quot;emulate or redirect the communication protocols used by Valve in any network feature of the Content and Services, through protocol emulation, tunneling, modifying or adding components to the Content and Services&quot;. I doubt that Valve would ever agree, since such a program could very easily be used to create spam bots that works bombard users with unsolicited advertisements, but maybe Valve would be willing to cut deals with AAA video game companies to let them deploy tools to automatically manage their store pages.
It depends on what you are selling to the enterprises. You could be selling just a licence to use the program, and retain all the rights on the source code. You could be selling the rights to the source code. For #1, the source code is yours and you can do what it pleases with it1. In fact many programs offer both an open-source licence (which usually forces the user to make its changes to the code publicly available) and a commercial one (which allows the user to keep the modifications of the source code for themselves). For #2, the source code is no longer yours so it is not up to you to decide what to do with it. 1I am assuming no other agreements imposing limits on those; for example that none of your contracts to your customers have a clause forbidding you from making the code available to the public.
The price is not one of the terms and conditions of the CC-SA license. You may chose to attach a price to a derivative work (which you have the right to create under license section 3.b). But any person who receives the derivative work legitimately (from you or from someone who got it from you, directly or indirectly) must get it under the CC-SA license, and has the right to redistribute it, and may do so at no charge if that person so chooses. Also, you may not impose any copy protection or other technological measure that would prevent exercise of the reuser's rights. Whether selling a work that may be redistributed freely is good business is your decision.
IANAL, just a programmer with an interest in legal rules. Due to the very permissive nature of the MIT license, no, it does not appear that anything illegal has been done. Specifically, the section to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software (emphasis mine) grants everyone the right to modify your code and share those modifications, provided one includes the license. Since this person has included your license (including your copyright notice), they have followed the conditions of the license and are able to share your stuff. Legally. Ethically, I still think its ****. This might be a good starting point in selecting a license (note the Modification column). https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses The CC-BY-SA license family, as mentioned by Ron Beyer in comments is on this list, for example. TL;DR: You unfortunately granted a more permissive license than what you wanted/needed to. This was a BadThing(TM), analogous to giving too broad of access rights to a method or class. Determine your desired permissions, then select a license that matches what you'd like to grant.