can I get sued without accepting EULA I plan publishing information in an article about Software which is the result of people reverse engineering the software. The author of the software has been attempting to sue people who made use of the information because it is against the EULA. I do not have the software myself nor have I ever accepted the EULA. I am only using information I found on the internet (public websites, etc.) and write my article based on my researches. My question is: Can I be sued for doing this because it is against the EULA which I never accepted? The reason I am doing this is because it is a security threat for the users of the software however it needs more attention in order to be addressed by the company.
No. You cannot be held liable for violating the EULA if you have never used the software and are only reporting what people who did use it told you. Of course, people bring groundless lawsuits all the time and you might have to defend such a lawsuit if you are sued. In some places you could be subpoenaed to disclose your sources, and in others, a reporter's privilege would allow you to quash such a subpoena.
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.
Is it a violation of copyright to publish a computer program that exactly produces such a piece, without containing the piece itself in the program? Yes. A program that reproduces a particular work is functionally a derivative work and is a copyright infringement. A program that composes music not tied to a particular work would be patentable, but the algorithm would not be protected by copyright, although derive works based on the code implementing the algorithm might be protected by copyright. Of course, this assumes that the person devising this algorithm knows about the original work that it will produce. If the person devising and the person using the algorithm are ignorant of the existence of the prior work that it produces, it is not a copy or a derivative work and is not infringing. The source of the creation of an allegedly infringing work in relevant in copyright law even thought it is not relevant in patent and trademark law. Copyright protects independent inventors of the same work from infringement liability, although this may be hard to prove. In theory the burden of proof to show copying is on the personal bringing the lawsuit alleging infringement. But, a copyright infringement plaintiff can meet their burden of proof in a copyright case by inferring that copy was made from the circumstantial evidence of the allegedly infringing work's similarity to the allegedly infringed work without direct evidence of copying or deriving the work from the original work.
Under your proposal, the author cannot effectively use the software at all, much less sell his creative efforts. The EULA clearly states that copyright is automatically transferred to the vendor when a document is created. The author gets started, writes &quot;It was a dark and stormy night&quot; then has a moment of writer's block, saves and closes, takes a walk, then tries again. The author has transferred copyright in the work to vendor, and needs vendor's permission to make revisions. So you have to tweak the EULA to grant automatic permission to author to create derivative works (revisions), and to distribute. A more effective strategy would be to impose a revenue-sharing formula on any commercially-exploited work created using the software, rather than attempt to directly seize the intellectual property. The CC &quot;NC&quot; license attribute is a distant version of what you are looking for - it prohibit any money-making use of the software. What you would add to that is a condition that the software can be used commercially, provided a certain compensation be rendered. You would of course have to be very clear in advance about what was actually agreed to.
The GPL does not forbid you from charging money for software, nor does it require you to provide source code to the general public. What the GPL requires is that your software be free software, with "free" used in the sense of "free speech" rather than the sense of "free beer." According to the Free Software Foundation (authors of the GPL), the right of users to sell software is a requirement for it to be free software. If you receive a GPL license for software, you can give it to whoever you want provided you also ensure that person can get the source code. You don't need to make the source code available to the public, only to the people you actually distribute the binaries to. The GPL is structured along the lines of "if you distribute the software to someone, you must give them these rights;" it is not structured along the lines of "you must distribute the software." Of course, if users have the right to distribute copies for free, it's hard in practice to charge money (all it takes is one user distributing copies). But that doesn't mean you can't try. Some companies make substantial money selling free software through various models (e.g. Red Hat, which charges money for support). Others might bank on the fact that plenty of people are willing to pay to get it from the official site, and aren't interested in finding a free copy somewhere. It doesn't matter; as long as they license the software to you under the GPL and give purchasers access to the source code on the same terms, they're in the clear (if you want to redistribute binaries, it's your job to redistribute the source code as well).
Yes, but ... It doesn’t protect you. Let’s imagine you put such a clause in and a person in Europe used your service notwithstanding: they’ve broken the contract but you’ve broken the law. You get the fine and they get ... nothing. Because you can’t contract outside the law you never had a valid contract with them so you have no basis to sue. Further, because you are purporting to something you can’t legally do, you are probably on the wrong side of misleading and deceptive consumer protection law: which is another fine. If you can ensure that you don’t breach local law - like by not operating over the internet - then you can choose not to deal with e.g. Europeans. If you can’t guarantee that, then you’re stuffed.
It is illegal to make copies of copyrighted materials without license. In the case of software, obviously it will be illegal to make copies by copying and installing the software without a license, but we are not talking about that. If I have a legitimate license of say Photoshop, and I start the application, parts or all of the code will be loaded into the RAM of my computer, which is a copy. According to copyright law, it is legal for me to make that copy. You are allowed to copy legitimately owned software into RAM to execute it. If your copy of Photoshop is illegal, and you start the application, the copy that is made into RAM is again copyright infringement. Having read the software license for the software that you get when you buy a Mac, it seems that if you steal my computer and just start the operating system, you are committing copyright infringement, and it seems that if you buy such a stolen computer and just start the operating system, you are committing copyright infringement as well, because the license that I received when I purchased the computer covers anyone using it with my permission, and covers anyone who legally buys the computer from me, but doesn't cover a thief. Now does this affect the work that you did? No, you have the full copyright on your work. Copyright law doesn't require that your tools are all used legitimately.
By &quot;unlicensed&quot; you mean that it doesn't state a license for use (MIT, GPL, etc.)? Those licenses are just a codified bundle of terms of use that cover many many edge cases. You have in place a much simpler agreement that covers the primary situation: you using/modifying the code for your own use. It's just like borrowing a car. You will ask a friend &quot;hey, could I borrow your car for a bit?&quot; &quot;sure!&quot;. You know there's a possibility that you'll get in an accident or something weird will happen, but you think the chances of that are minimal and you would be able to work it out. If you ask a car rental company, they'll give you a full contract covering every situation that may happen. Similarly, a large company would be hesitant to borrow a car for corporate use without a legal framework surrounding it. So you will likely be in the clear if you are just using it for a small project with minimal legal/financial implications. If you plan on turning your project into a multi-billion dollar empire, you should revisit your agreement.