Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by Natsu on Friday June 03, 2016 @02:01PM
(#11832016)
I think we'd be better off if we were the ones suggesting ways to define unauthorized access. I've thought about this quite a bit and I posted something on that subject about a week ago with my own suggested definition thereof. Quoting from that earlier comment:
=====
For 'unauthorized access' to a computer system you (should) need to knowingly access a protected system in a way not permitted by the rights granted to you by the computer system, or by deliberate deception of either the computer systems or people.
So for 'knowing' we have to actually know (via banners, etc.) that we're somewhere we shouldn't be. For 'protected' it has to be actually protected (none of this "I found unprotected files lying around with no password" nonsense). The last two clauses cover privilege escalation attacks and social engineering. So it should matter if you're operating the system normally or if you accidentally just click/type something wrong and found your way in vs. you were deliberately hacking / social engineering your way in.
I'd also add a safe harbor for anyone who in good faith reported the issue to the site operators, police, or government regulatory bodies to prevent reprisal like this ugly case.
Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by JumpCrisscross on Friday June 03, 2016 @01:20PM
(#11831675)
I just emailed my Senators. People routinely underestimate the value of calmly and briefly explaining to elected leaders why they should vote one way or another.
Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by awinter-py on Friday June 03, 2016 @09:32AM
(#11830193)
holy crud! CFAA already allows TOS writers to define any behavior as unauthorized & therefore a felony. Congressmen need a way to look strong on security without completely breaking rule of law. We should issue them nerf guns or something.
Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by sathackr on Friday June 03, 2016 @11:42AM
(#11830959)
Wasn't that the very basis of the Aaron Schwartz case? That, by violating the terms of use of the MIT site, he was violating the CFAA thus charged with multiple felonies?
The linked case dealt with employees but I don't see why there should be a distinction. I would consider the general public to have even greater protections.
Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by two2two on Friday June 03, 2016 @12:45PM
(#11831420)
This is a little different as it has to do with exceeding authorized access as an employee.
The CFAA doesn't allow TOS writers to "invent" felonies, but it does allow for a basis of prosecution against someone who breaks it.
Someone who siphons off data, breaking a TOS, will get treated the same as someone who lies on their dating profile. This is why the CFAA is too vague in its current form.
We're expected to trust that only the "big guys" will be prosecuted under the CFAA, skirting the point of having the rule of law in the first place as no interpretation of a law should be left up to the discretion of a few men.
As well, most people break at least 3 laws a day without knowing it, and they're likely breaking many more throughout the day online, just not getting prosecuted for it, but they could.
Re:EFF Joins Coalition Opposing Dangerous CFAA Bill
by beardog on Friday June 03, 2016 @05:58PM
(#11833580)
Good news everyone, i hid a <img> to my server in this page, now you visited part of my site you were not authorized to! You are now all felons, see you in court.
Learn: https://wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act
Call your representatives: TryVoices.com
Donate to the EFF: https://supporters.eff.org/donate/
=====
For 'unauthorized access' to a computer system you (should) need to knowingly access a protected system in a way not permitted by the rights granted to you by the computer system, or by deliberate deception of either the computer systems or people.
So for 'knowing' we have to actually know (via banners, etc.) that we're somewhere we shouldn't be. For 'protected' it has to be actually protected (none of this "I found unprotected files lying around with no password" nonsense). The last two clauses cover privilege escalation attacks and social engineering. So it should matter if you're operating the system normally or if you accidentally just click/type something wrong and found your way in vs. you were deliberately hacking / social engineering your way in.
I'd also add a safe harbor for anyone who in good faith reported the issue to the site operators, police, or government regulatory bodies to prevent reprisal like this ugly case.
Sadly, I don't get to write these laws.
https://en.wikipedia.org/wiki/United_States_v._Nosal
(Further: even without that case, CFAA never allowed TOS writers to invent their own felonies).
The linked case dealt with employees but I don't see why there should be a distinction. I would consider the general public to have even greater protections.
The CFAA doesn't allow TOS writers to "invent" felonies, but it does allow for a basis of prosecution against someone who breaks it.
Someone who siphons off data, breaking a TOS, will get treated the same as someone who lies on their dating profile. This is why the CFAA is too vague in its current form.
We're expected to trust that only the "big guys" will be prosecuted under the CFAA, skirting the point of having the rule of law in the first place as no interpretation of a law should be left up to the discretion of a few men.
As well, most people break at least 3 laws a day without knowing it, and they're likely breaking many more throughout the day online, just not getting prosecuted for it, but they could.
https://www.eff.org/files/2016/05/25/114th_may_2016_whitehou...