Is brute forcing the password of an encrypted file legal? A person I know sent me an encrypted .zip archive and I do not know what data is inside. Is it legal to break the password and open the archive, for example, by using a brute force algorithm? The algorithm may need a long time, but it will reveal the password that was used for the encryption. The file was sent directly to me and I know that I am meant to be the recipient. I assume that the file was protected by accident. Would the answer be different if I am not the intended recipient and someone sent me the file by accident? We both live in Germany.
If you aren’t the intended recipient of the password-protected file: StGB § 202a makes it illegal to access this file StGB § 202c makes it illegal to obtain (e.g., by brute forcing) the password for this file, if you intend to access the file that way (in the sense of § 202a) (this is the so-called hacker paragraph) If you are the intended recipient, this law doesn’t seem to apply, and it shouldn’t be illegal to brute-force the password.
It's not illegal to ask. Whether they can give it to you, and under what circumstances, is another, much more complicated matter. For instance, if the database contains health information covered by HIPAA in the United States, or personal information covered by laws like GDPR or CCPA, the customer's ability to share the database may be restricted, either requiring additional confidentiality obligations/use restrictions, or preventing sharing entirely.
It would be illegal because only you are allowed to view the comic you purchased. Creating a copy of your comic (e.g photcopying, scanning etc) is not allowed, and showing others a copy of your comic is also not allowed
It's possibe to cover auto-starting apps and cookies under the definition. I'm not convinced and could argue against that but I don't think it matters. The tiny extract you linked isn't a law. It is a definition. It does not say &quot;these things are illegal&quot;. For that, we have to zoom out a little. Section 43 includes the offense in question (emphasis mine): If any person without permission of the owner or any other person who is incharge of a computer, computer system or computer network... introduces or causes to be introduced any computer contaminant or computer virus... So back to the question. Could Steam be considered a virus? Maybe. Is it illegal? No. On the other hand, if I were to gain access to your computer and download Steam, yes that could be an example of breaking that law.
Yes So far so good. This is a copyright violation but it is probably fair use - certainly there is case law permitting a copy of a backup digital asset to be made so I don’t see why a similar argument wouldn’t work with backing up a physical book. Clear copyright violation. Alice can rent out the original under the first sale doctrine but the ‘backup’ is not so protected. It’s not fair use because it’s use is commercial, the work is a type of work the author expects to profit from, the entire work has been copied and the use is deleterious to the market i.e. the renters are less likely to buy an original - it falls foul of all four factors of the fair use test.
I realize it has been eight months, but I believe I can offer an opinion. Given the nature of the question, please keep in mind that I am not a lawyer and my opinion is no substitute for professional legal counsel. [Preparing this post has been an educational experience and my opinion should in no way be interpreted as expert opinion] Assuming you have not infringed on any patents, the relevant legal challenges Valve could try include breach of contract, copyright infringement, and trade dress infringement. Breach of Contract The potential breach of contract occurs because the Steam client setup application requires you to accept a contract of adhesion (The License) before the software can be installed. I could not find a copy of The License online in plain text (this is separate from the Steam Subscriber Agreement, which you also agree to by accepting The License), but you can read it any time by running the Steam client setup application which is available at [redacted due to low rep - the Steam website]. These so-called "shrink wrap licenses" are of questionable legal value, depending on how the licensee assents to the contract. People often bring up Specht v. Netscape Communications Corp. In that case, the only reference to a license was on the download webpage, and it was only visible if the user scrolled down past the download button - Netscape argued unsuccessfully that clicking the download button indicated assent to the terms of the license. The Steam client setup application has a prominent dialogue box showing the terms of The License and requiring your explicit assent before installation can continue. A more relevant case may be ProCD, Inc. v. Zeidenberg, where the Seventh Circuit ruled that a license agreement was valid where the licensee had to click on a dialogue box assenting acceptance to the agreement. In short, you may be required to defend yourself under the terms of The License. If the licenses are thrown out as unenforceable, the prosecution would probably move towards copyright infringement. Section 1 Paragraph C of The License states (emphasis added): Except as expressly set forth elsewhere in this License Agreement, you may not, in whole or in part: copy, photocopy, reproduce, translate, reverse engineer (with the exception of specific circumstances where such act is permitted by law), derive source code from, modify, disassemble, decompile, or create derivative works based on the Program. Now you assert that there has been no reverse engineering, that you made yours "completely from scratch using completely different styling and images (even different website inside the client that is mine)". You may be challenged on these claims in court, for example comparison of source codes could rule out reverse engineering. I will touch on derivative work status later. Note that under Section 5, the provisions of Section 1 Paragraph C do not apply after you have uninstalled the Steam client software. This means in the case that you [can prove you had] uninstalled the Steam client software before making your own client, you would have a defense to breach of contract under Section 1 Paragraph C. However... The License also includes the terms of the "Steam Agreement", viewable online at http://www.steampowered.com/agreement. The Steam Agreement takes effect when you register for your Steam account. Section 2 Paragraph G of the Steam Agreement echoes the above referenced Section 1 Paragraph C of The License, and even survives termination of the Steam Agreement (your steam account being cancelled). Now assuming you can provide defense against reverse engineering, you may need a defense against the charge that your work is a derivative work. Your case may be pretty strong if you can show that your client was indeed written from the ground up - which rules out the possibility of deriving your program code from Steam's code as literary copyrights go. The prosecution could try saying you have copied the audiovisuals of their program, but your program was written "from scratch using completely different styling and images". Eventually prosecution may have to move into trade dress infringement. Copyright Infringement In a case of alleged copyright infringement, the first order of business is to prove there is a copyrighted work to begin with. The work in question is the Steam client by Valve Corporation. Again, I am not an expert but I could not find any copyright registration for the Steam client (http://www.copyright.gov/records/ -> Post-1978 Records -> Search by Name "Valve Corporation"). Copyright registration is required before infringement suits can be filed. Valve can register after infringement occurs but they will be limited to actual damages and profits. Nevertheless Valve does claim copyright over its product. A notice is posted on The License and Steam Agreement, and from the client itself the Help menu contains a command "Legal Info" which opens a webpage containing a copyright notice. Since 1979 it has not been necessary to post a copyright notice, but a notice helps break a defense of innocent infringement. You imply that you copied elements of the Steam client "to give customers a similar feel to what they are used to [the Steam client]". In your specific case innocent infringement may not be a valid defense. It seems you are most concerned about copyright infringement over the menus. An extremely relevant case is Lotus Development Corp. v. Borland International, Inc. In that case the First Circuit held that the menu heirarchy for Lotus 1-2-3 (the progenitor of virtually all menu heirarchies today) was uncopyrightable as a "method of operation" under U.S.C. 17 Section 102(b). We think that "method of operation," as that term is used in [U.S.C. 17 Section] 102(b), refers to the means by which a person operates something, whether it be a car, a food processor, or a computer. Thus a text describing how to operate something would not extend copyright protection to the method of operation itself; other people would be free to employ that method and to describe it in their own words. Similarly, if a new method of operation is used rather than described, other people would still be free to employ or describe that method. We hold that the Lotus menu command hierarchy is an uncopyrightable "method of operation." The Lotus menu command hierarchy provides the means by which users control and operate Lotus 1-2-3. If users wish to copy material, for example, they use the "Copy" command. If users wish to print material, they use the "Print" command. Users must use the command terms to tell the computer what to do. Without the menu command hierarchy, users would not be able to access and control, or indeed make use of, Lotus 1-2-3's functional capabilities. If specific words are essential to operating something, then they are part of a "method of operation" and, as such, are unprotectable. This is so whether they must be highlighted, typed in, or even spoken, as computer programs no doubt will soon be controlled by spoken words. The Supreme Court affirmed the decision with an even court (Judge Stevens recusing), so no national precedent was set. Nevertheless the ruling has not been overturned - the First Circuit goes into great detail explaining their decision, and I do recommend reading the ruling. We have already discussed derivative works and reverse engineering with contracts, and the same defense would apply under copyright law: source code comparison. Trade Dress Normally things like design and layout are left to patent law. A desperate prosecution, however, may claim that by copying their "look and feel" you infringe on their trade dress. The relevant text is part of U.S.C. 15 Section 1125(a) (emphasis added): (1) Any person who, on or in connection with any goods or services, or any container for goods, uses in commerce any word, term, name, symbol, or device, or any combination thereof, or any false designation of origin, false or misleading description of fact, or false or misleading representation of fact, which- (A) is likely to cause confusion, or to cause mistake, or to deceive as to the affiliation, connection, or association of such person with another person, or as to the origin, sponsorship, or approval of his or her goods, services, or commercial activities by another person, or (B) in commercial advertising or promotion, misrepresents the nature, characteristics, qualities, or geographic origin of his or her or another person's goods, services, or commercial activities, shall be liable in a civil action by any person who believes that he or she is or is likely to be damaged by such act. (2) As used in this subsection, the term "any person" includes any State, instrumentality of a State or employee of a State or instrumentality of a State acting in his or her official capacity. Any State, and any such instrumentality, officer, or employee, shall be subject to the provisions of this chapter in the same manner and to the same extent as any nongovernmental entity. (3) In a civil action for trade dress infringement under this chapter for trade dress not registered on the principal register, the person who asserts trade dress protection has the burden of proving that the matter sought to be protected is not functional. Defense against such a claim would be showing that the elements of Steam's "look and feel" were adapted because of functional reasons - see example rationale in the previously mentioned Lotus v. Borland. Overall, so long as you did write the program from scratch and there are no patent violations, you have in my opinion a strong case. There may be moral questions about unfair competition (why should you be allowed to capitalize off Valve's work put into the Steam client?), to which I would point out that your product does not appear to be in direct competition with the Steam client. Without direct competition or confidence in evidence of IP infringement it is quite unlikely Valve will file suit against you. If you would rather avoid even the possibility of legal action, you could always contact Valve directly and ask for a license.
Copying is illegal, creating an identical work by coincidence isn't. If it is not a criminal case, then a court decides whether it is more likely that the identical work was created by copying or by coincidence. Creating an identical work through a random process isn't going to happen, claiming this would be an awful defense. On the other hand, it is quite possible that two software developers using very stylized code adhering to struct coding conventions can produce quite large bits of identical code. Your links titled "metadata" and "hash" don't actually link to a description of metadata, or the description of a hash, but to a description of torrent files, which is something totally different. Systematically distributing files whose only purpose is the illegal duplication of copyrighted works should not be done without consulting a lawyer, as has been said on other threads (whether posting links to copyrighted files is legal). The chances that a random process will generate a file identical to an existing copyrighted file of say over 100 bytes are virtually zero. If there is an illegal copy of a copyrighted file, and you claim that you created it through a random process and coincidence, you will lose, and deservedly so.
In the UK and USA (and I imagine other jurisdictions) there have been laws that explicitly provide for orders obliging entities to (A) provide access or information and (B) keep the order secret. For example, in the USA the Stored Communications Act, Fair Credit Reporting Act and Right to Financial Privacy Act authorise the FBI to issue National Security Letters (Wikipedia, EFF, EPIC, Lawfare). These are an administrative subpoena, without prior approval from a judge, for meta-information (e.g. phone numbers dialed or email recipients addressed but not the content) of communications relevant to national security investigations. They typically contain a non-disclosure requirement prohibiting the recipient of the NSL from disclosing its existence or the FBI's demands. There have been challenges on First Amendment grounds to the non-disclosure aspect but, so far as I'm aware, they have all ultimately failed. Some of their non-disclosure requirements may eventually expire under other laws. In response, so-called 'warrant canaries' (Wikipedia) have been developed (and gone a bit further than the original idea) - these are intended to allow entities to relatively passively warn of such an order having been received if not the detail of the order. However, they can be legally risky in that they might be seen by a court as trying to circumvent the non-disclosure requirement and therefore breaking it.