12 ms·
The CFAA Reaches the Supreme Court, Sort Of
- tbrownaw 11y agoNot really, per TFA this seems to be more about handling procedural goofs than about the particular law they goofed up on.
- AnthonyMouse 11y ago> The difference between “access without authorization” and “exceed[ing] authorized access.” I never really understood why this distinction is considered so contentious. The law itself defines "exceeds authorized access" as "to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter." Which isn't that helpful because it's approximately what you would expect it to mean if it wasn't defined. But I'm not sure where the ambiguity between "access without authorization" and "exceeds authorized access" is supposed to come in. The plain meaning is clearly that in one case you have no legitimate access (i.e. the system doesn't allow anonymous access and you have no account) and in the other case you have some legitimate access but not to do what you did. Kerr makes the argument that it is possible for "access without authorization" to imply "exceeds authorized access", but that is one place where the statutory definition is useful: The definition of "exceeds authorized access" first requires you "to access a computer with authorization..." The real trouble with the CFAA is that it doesn't make the scope of authorization clear in either event. The canonical way people know whether they're authorized to do something to a computer system is that it allows them to do it. If you aren't authorized then it comes back with "access is denied" and you can't do it. So the only way to break the law is to get the computer to do something it isn't supposed to let you. But where is the definition of that? How are you supposed to know what the computer is supposed to do, if the normal way of knowing that is to look at what it actually does, and the only cases that matter are the ones where that doesn't apply? There may be some obvious cases (e.g. logging in with someone else's account), but by what rule or principle are these cases supposed to be distinguished from others?
- adanto6840 11y agoThis really hits the nail on the head. Does sending an HTTP request and receiving an HTTP 200 response code indicate that you're authorized? IMO, yes. What if you send 5 million requests over the course of X timeframe, each of which also receives an HTTP 200 response. Have you "exceeded authorized access" at that point? IMO you haven't -- but right now the answer is basically, "maybe, TBD on a case-by-case basis" which is a decidedly poor answer. And, as you eloquently summarized, that's precisely the problem with this part of the CFAA. Unfortunately I don't think that the outcome of this specific case will do much to clarify this aspect of CFAA. That said, the final opinion could possibly shine a bit of light in the right direction if we're lucky, but I'm not holding my breath for a black-and-white interpretation any time soon...
- cookiecaper 11y ago>Does sending an HTTP request and receiving an HTTP 200 response code indicate that you're authorized? IMO, yes. It'd be a boon for anyone who depends on data scraping (which includes basically everyone in some form or another) if the Court decided that issue in that way, but I agree that it seems really unlikely that that will be broached in this case. Meanwhile, big companies will be able to scrape to their hearts' content while small companies are forcibly shut down for the same when one such big company retains a big law firm to intimidate an upstart they're afraid of with the threat of a lawsuit that costs millions just to litigate, excluding any potential damages. If the small company were to attempt to use the same law(s) to defend themselves, they'd be guaranteeing themselves said millions in legal fees, as the big company will aggressively defend itself, so it's not really an option. License to bully for the rich, bupkis for everyone else. That's how legal gray areas work.
- snowwrestler 11y agoThat would certainly make life easier on technologists--just read the HTTP code and if it's 200 you're good. But the legal concept of authorization doesn't rest on technology, and there's actually a good reason for that: if the technology was that reliable, then you wouldn't need the law at all. That is, if servers always returned a 401, 403, 511, etc. status code for unauthorized access attempts, then it would be impossible for unauthorized access to occur. And we don't tend to bother with laws restricting impossibilities. But we all know the reality: people are imperfect and therefore so is their technology. A server could return a 200 status on a page that you are not authorized to see.
- jevinskie 11y agoIf the law says A | B, and someone is convicted of A & B, is it not plainly obvious that the jury would have convicted of A | B as well, since it is a strictly "weaker" predicate?
- AnthonyMouse 11y agoThe argument is from the other side. The idea is that the prosecutor clearly didn't prove A & B, so the jury didn't follow the judge's instructions. If the judge had told the jury A | B then the jury's verdict would have been more reasonable, which hurts the defendant's argument that it was unreasonable.