The CFAA is a very bad law, but it's hard to resolve "authorized" versus "unauthorized" deterministically without coming up with absurd situations. I think a better thing to look at is CFAA sentencing and severity, which currently scale up with the counter in your "for()" loop and quickly produce dizzying penalties for minor offenses. Taking the piss out of CFAA sentencing would also reduce the incentive that US Attorneys have to throw the book at petty offenders.
Like in other cases when computers meet the law, it's often a "colour of bits" distinction. I recommend this article:
The CFAA is a very bad law because it's hard to resolve "authorized" versus "unauthorized" deterministically without coming up with absurd situations. Imposing only misdemeanor penalties would certainly resolve the issue in practice by depriving the failure of its teeth, but it still wouldn't make it a good piece of legislation.
If someone subverts an authentication system to get authed, then they were clearly never authorized no matter the granted access to the data.
Seems unauthorized or not is baked into the web already. It is the humans behind corporations and their lawyers trying to stretch the definition or create new mechanics. The AT&T case shows this for sure.
If I leave my apartment door unlocked, and you go in while I'm at work and steal my television, you are still liable for unlawful entry and burglary. There is no legally admissible argument that my not having locked the door confers upon you authorization to go through it.
Of course, that's a much clearer case than API access tends to be, but the point I make from it is that "nobody stopped me from getting to this" does not imply "it must be lawful for me to make use of this".
Slap on some authentication before calling the lawyers. Lawyers are needed for when such systems have been subverted.
Seems the reality distortion of blaming anyone that touches something a corporation doesn't want touched is catching on. Persons behind corporations that dispatch lawyers with great zeal are responsible for conflating their own mistakes for exploitation.
For those having a hard time, just think like the NSA: Public unencrypted data will be used, but not always in the way the persons who made it public contemplated.
Oh god, this again
Many on HN seem like to feign ignorance when it comes to intent. Have fun playing dumb in court when you try to bring out your strictly technical argument why you should have legally downloaded all of those credit card and social security numbers since you "could".
All analogy is terrible if we're talking about computer access.
The door analogy fails because there are two existing sets of laws covering both sets of circumstances, and how the courts interpret authorized access might have very little to do with what normal people would mean.
By having a website on the public facing Internet with no access controls you are inviting anyone to view that page. You are giving implied consent to view that page. Except that's not how some courts interpret it, so my opinion means very little.
It's also a technical non-starter, because the HTTP status code that accompanies a response is an artifact, not a promise; the result of a SQL injection attempt could for instance very well have a 200 code on it.
If you don't want someone to have something, don't have your system dispense it when they ask for it.
But yes, intent does come into it - and that's often the problem - people investigating systems for curiosity or academic interest or because the system owners won't take them seriously when they have reported problems that put people's data at risk and want to demonstrate it are treated like criminals (often charged with felony offences with potential jail time worse than assault or theft)
As per other people's comparisons, some things are implied restricted: credit card information of another individual is not for you to see. The door to a bathroom is closed: If no one is in it, you may enter, if someone is using it, usually not.
I think in the bathroom analogy, it's clear that 1: A person should lock the bathroom door if they want privacy and 2. An individual may want to knock if a door is shut instead of trying the door.
Therefore, engineers should explicitly restrict access to certain data (rate limits, terms of service, passwords etc..) and people working on projects and what have you may want to actually ask: (is it ok, if I do this?)
Putting things into a state wherein they get auto-served to any request is something akin to posting documents inside your front window for passerby on the sidewalk to see.
The whole thing's a fucking terrible analogy though, and every time I see it trotted out to support some "if I leave my doors unlocked" argument I die a little bit inside.
People like to make this debate more complicated than it really is, what with the warring analogies. Really, the issue is straightforward: did the person accessing the information have a reasonable belief that they were authorized to access it?
Your argument is, "if the webserver says it's OK, then my belief that I'm authorized is reasonable". That's a sane argument, but has any court ever agreed with it?
Oh god this again
When you send a request to a machine owned by a person and it responds with data that person doesn't want you to have, it is not your fault for sending the request - EVEN IF YOU KNOW/SHOULD KNOW/COULD REASONABLY BE EXPECTED TO KNOW/ETC THE PERSON DOESN'T WANT YOU TO HAVE THE DATA.
The inherent flaw in this interpretation is that it uses a self-referential definition of authorization. Saying "access is authorized if it is reasonable to believe that access is authorized" is meaningless. You would need an independent definition of authorized access in order to evaluate the reasonableness of the belief, which defeats the purpose of using it to define authorization.
Where a "reasonable belief" standard makes sense is in determining intent, not in establishing the definition of an element of the crime. For example, it may be illegal for you to steal my laptop (where the definition of the elements of theft are fairly rigorous), but if it turns out that you have exactly the same model of laptop and "reasonably believed" mine to be yours then even though you objectively stole my laptop, the prosecution may not be able to prove that you intended to.
But "authorization" is clearly not about intent. The alleged perpetrator is not the one permitted to define the scope of authorization, so their intent is irrelevant in determining whether the access was in fact authorized, and the intent of the owner of the computer system is also irrelevant because it isn't reasonable to subject a defendant to the intent of a third party if that third party fails to clearly articulate it. What matters instead is what has been articulated -- the information made available to users of the computer system about what level of access is permitted.
But then we're back to the terms of service trouble again. If you allow contractual restrictions to define authorization then you're allowing corporations to define the contours of a federal felony and anyone who lies about their name on Facebook can be thrown in prison at the whim of an overzealous prosecutor. Conversely, relying on technological authorization makes the law extremely narrow (capturing only the likes of perpetrators who defeat technological denials of authorization via e.g. physical intrusion into the victim's data center -- although that would align better with the established penalties). Neither seems particularly satisfactory, and the reason is that "unauthorized access" is the wrong thing to prohibit. "Authorization" is vague and subjective, and the specifics of a violation span such a wide range of conduct and misconduct that lumping them all together under the same set of penalties is all but guaranteed to violate proportionality unless the penalties are set so low as to make the prohibition nominal.
And I still don't understand what useful purpose it serves as distinguished from the already-existing penalties for vandalism, fraud, misappropriation of trade secrets, etc. etc. If someone engages in access without authorization, without more, the warranted level of punishment is minimal and almost never even worth prosecuting. If they engage in some further malicious act then the penalty for the greater crime can be imposed and unauthorized access is only a side show and a dangerous instrument of prosecutorial overreach. When is it ever supposed to be useful in proportion to the controversy and abuse it produces?
Did you typo a wget to random URL and it returned my credit card number / ssn and home address, realized this was something you shouldn't be accessing and stop? I'm sure you would have a good case that your intent was merely an accident or innocent and you won't get in trouble.
Did you wget a million URL's over the course of the day and store these credit card numbers / ssn's for some use later? Probably might have a harder time justifying that. Again it is all about context and intent, these are going to be a factor in the court. It is never going to be a simple black or white sequence of events that can be followed to determine if you were doing something harmless or not, no matter how much the crowd here doesn't want that to be the case.
But there is a difference between the definition of a crime and the intent to meet that definition.
Let's try an analogy. Suppose I go to a local retailer and tell the clerk that I'm a professor at the local university and ask her to record the name, address, credit card number and other information of everyone who buys something in the shop for me today because I want to collect some statistics. There are now two issues here.
The first issue is whether the clerk agrees to provide me with the information. The shop owner and the credit card company need for her to not agree to this because it is clearly a security vulnerability. Even if I really am a professor collecting statistics for my research, she can't know that for certain, and I could be a scam artist out to commit credit card fraud. But let's suppose the clerk hasn't been properly trained and she gives me the credit card numbers. The obvious analogy is to a misconfigured web server.
At this point it matters quite a lot what I do with the credit card numbers. If I'm a scam artist and start making fraudulent charges to the cards, there ought to be significant penalties. But if I really am out to do statistical analysis on local retailer purchasing behavior, should there be? Or should the retailer just take the opportunity to retrain the staff? There is a strong case for a lack of penalties -- because intent does matter. Which is the fundamental problem with the CFAA. It doesn't require the intent to commit a malicious act, only a vaguely defined lack of authorization to commit any act regardless of whether or not the act is malicious.
Edit: My original comment further up in this thread hinted at this difference and how lawyers seem to be trying to shift the line so unwanted access by a user is treated the same as exploitation of the data within even if the data was not exploited upon.
Rather sure it does, some crimes like credit card fraud are separate from unauthorized access of the computer systems the information came from. Exploiting the data is not the same as exploiting to access the data.
Lawyers are deployed to push their client's POV, wins or losses may "shift the line" regarding how written laws are upheld in court. Which in my opinion is used by some as a chance to defray from responsibility to properly administer public facing systems.
http://www.law.cornell.edu/uscode/text/18/1030
Perhaps it would be simpler if you just pointed to the part of the statute you're referring to, because I don't follow your argument.
Sir your analogy doesn't mesh with reality as another commenter above noted. Servers provide responses, not hand over the hard-drive.
Calling people children is absolutely negative and is a detriment to any reasonable discussion, which is what this site seems to be about. Very kindly shut your gob if you want to continue this route.
Stop being such a negative jerk when communicating with others.
Edit: Thanks whoever down-voted the guy saying "fuck" but not the user injecting insults and slights. This HN community feels healthy and mature.
One of my weekend projects involved stripping actor, genre, and director information from IMDB for the AFI Top 100 movies. The prototype was simplistic but still gave some interesting data to mine (e.g. Robert Duvall has been in the most AFI Top 100 films, credited 6 times).
The next step of the project would be to strip more data from IMDB, but I hesitated since I didn't want to get my IP banned or something. I had never considered that what I was doing could potentially be illegal.
If you're worried about that I would use something like a DigitalOcean droplet. If your IP gets banned, at least it's not your home IP.
I believe AT&T did send such a letter.
It's just like when you're discussing your entrepreneurial plans with a non-entrepreneur. Typically, their response is an eye roll and a sarcastic "Good luck!". Most people envy successful entrepreneurs really hard, but they have no patience for beginners. It's like they don't understand that there's stuff in between being a broke college kid and having a record-breaking tech IPO. The same is true for copyright infringers and web scrapers; demonstrate your value first, and then open discussions.
If Google strictly abode copyright or computer access laws, it would have never existed because it'd have to ask each website owner for formal permission to crawl their page and store records of their copyrighted material, including derivative works caused by compression, indexing, etc. (and worse the right to reproduce this content for display in search results) and meticulously record each copyright holder's assent. They'd have to verify that the legitimate copyright owner had provided assent, and not an imposter. They wouldn't be able to access anything because almost all boilerplate ToS documents forbid "automated access" and similar, and violating the ToS is illegal computer access.
Google is operating in a highly illegal fashion, and the only reason they're allowed to exist is because they demonstrated their value first by driving traffic to the copyright holders' websites. PayPal did the same thing with banking and payment regulations. At some point, you just have to recognize that most people aren't going to get it until you show them, and don't want to be bothered with your delusions of grandeur. It's better to ask forgiveness than permission.
What?!
If it's such a valuable service they could have given a cut to the authors instead of illegally copying their books. Allowing somebody to break the law because you believe they are morally good is textbook legislating from the bench and it's wrong.
That proposed deal did apply only Google, but it didn't preclude anybody else from negotiating their own deal.
Whoa there. At the time, the consensus was that anything put up on web servers was there for anyone to see by any means. Minus the 'robots.txt' convention for automated scanning, which existed because there were many other search engines before Google.
Is robots.txt a legally-admissible copyright release? There's probably more room to debate that one, but it's not clear-cut. What does it cover? Is it applicable to all crawlers? Can you do a general license release like that without your work effectively becoming public domain? What's the difference between a crawler and a human reader subject to standard copyright terms? What licenses are implicitly granted in a typical robots.txt? It's not like robots.txt is a verbose document that lays all of this out, and all of it is a potential legal problem point.
Also, Google assumes permission by default and only doesn't scan if you explicitly DISALLOW it with robots.txt. This is the opposite of copyright, which reserves a monopoly to the rightsholder unless he explicitly ALLOWS a certain use. It's undeniable that Google is violating copyright law millions of times each and every day, and that said violation is fundamental to their business.
And does any of this negate the computer access laws that make a site's ToS legally binding, even to those who don't formally agree to them? Strictly interpreted, Google would still be behaving illegally even if the copyright element was taken away.
I agree that there were search engines before Google, and that they mostly were in the same problematic legal situation.
To be clear, this is arguably the way that the Web almost has to work--but that doesn't make it all neatly legal under current copyright law.
If he had scraped the content to integrate into a movie torrent indexing site, he most likely would have run into legal difficulties. But since he was scraping the content to create a thought-provoking article about the kinds of interesting problems that Netflix is working on, it became PR gold for Netflix and they cooperated.
You can generally get away with a lot of things that would otherwise be actionable by simply considering the perspective of party that would have to act. In this case, he correctly reasoned that Netflix would rather see the article that was published rather than a "Netflix sued me for playing with their site."