Is it illegal to sell malware? Is it illegal to produce and sell malware? If no, is there any data I need to collect on the customers? Is it illegal to produce and sell Crypters(programs that hide other programs from antivirus)? If no, is there any data I need to collect on the customers?
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.
There is something called the exhaustion doctrine that says that once the holder of a patent sells a patented device, they have relinquished control over that particular instance of the patent implementation. Anyone who legally purchases this hardware has the right to run whatever software they want on it, as long the software is otherwise legal (software designed to defeat DRM would be an example of software that is is not legal).
A TOS is not intrinsically illegal, but an interpretation of a TOS may or may not be supported by a court, that remains to be seen. It probably does not constitute a &quot;deceptive practice&quot; under FTC standards. The TOS is your permission to use the software, and there can be no question that they have the right to impose conditions on customer use of the software. E.g. Amazon cannot freely use software that is only licensed for free educational use. They speak of &quot;ownership&quot; of IP so created and explicitly disclaim any claims about Current Law in Your Jurisdiction. At the crucial point in the agreement, they switch to talking about the license (BY-NC) that they grant when you are not a paid member. The exact details of this ownership are not part of the free tier TOS, but they do seem to add certain protections to &quot;owned&quot; content created under the Pro plan – they are under no legal obligation to make all content universally visible and usable.
Yes and No Selling your own body for sex is legal. Buying sex is illegal. Therefore the transaction as a whole is legal on the part of the seller and illegal on the part of the buyer. See Prostitution in Canada and Prostitution law in Canada. If you think this is odd, you are not alone '... one judge referring to the laws as "Alice-in-Wonderland" and the Chief Justice of the Supreme Court referred to the situation as "bizarre"'. In the circumstances, although I know of no case law on this, it would appear that any contract for prostitution would be void for illegality. Presumably, to enforce payment for services rendered the service provider would need to pursue a quantum meruit claim in equity.
I think haveibeenpwned would be legal in the EU because it carries out a task in the public interest (Art. 6(1)(e)), and it shares no more data then necessary, for example you can search for a password, but it would not show you the emailaddress which belongs to that password. It would also be legal for you to hold a copy of a leaked database, but only if you have a legitimate interest (Art. 6(1)(f)) to have it. Being a security company does not change that, but finding a legitimate interest might be easier. If you have a legitimate interest to hold a copy of a leaked database, it does not mean you can use it in any way you like. For example testing if the password still works, is very likely illegal everywhere in the EU. But I'm not familiar with the UK laws.
There is no case law as yet However, the most likely situation is that there is no copyright in the original works because they are computer-generated. There is certainly copyright in the code that created the art but the output of that code, the art itself, would probably not be subject to copyright. Copyright only exists in art created by humans. The US Ninth Circuit has held that animals cannot create copyrighted works. Subsequently, the US Copyright office has rejected applications for registration (a prerequisite to a suit in the US) of computer-generated art because it “lacks the human authorship necessary to support a copyright claim.” While this position has not been tested in the courts, I don't think they are any more likely to grant copyright to a program than they were to a monkey. What's going on? The OP states that there is litigation: there isn't. What there is, is a DCMA takedown request from Larva Labs. If this is complied with that will be the end of the matter; if it isn't then there may be litigation. However, before Larva Labs could sue CryptoPunks in the US they would first need to get a writ of mandamus to force the USCO to register it. If they try and fail then there will be a legally binding court decision that Larva Labs don't own the copyright in any of their computer-generated art. Which kills their business model and, presumably, them. This would be a very high-risk move. They may choose to sue in a jurisdiction where registration is not a prerequisite, however, that court would still need to be satisfied that there was a copyright that could be breached. So that's just a different take on the same problem. I have ignored the issue of NFTs as these are legally problematic in their own right and irrelevant to the main question. However, the NFT and the artwork are not the same thing.
Legal unless you violate copyright. Screenshots will probably be fair use. The manuals/how-tos need to be your originals, not copies from anywhere.
This seems to fall under &quot;Installation Information&quot; according to the GPL v3 license. &quot;Installation information&quot; doesn't need to be provided as source code, but it must be provided in such a way that others can take the source code, modify it, and make it work with the &quot;Installation Information&quot; that is provided. (Technical: At the place where the passwords and secure keys are entered in the source code, I would modify the code so that it doesn't build, followed by instructions how to create your own passwords and secure keys. So you try to build the program, it fails, it points you to instructions, you follow the instructions and change the source files, you try to build again, and it works).