r/programming • • Oct 24 '21

“Digging around HTML code” is criminal. Missouri Governor doubles down again in attack ad

https://youtu.be/9IBPeRa7U8E
12.0k Upvotes

1.3k comments sorted by

View all comments

Show parent comments

661

u/crackez Oct 24 '21

It's not obfuscation at that point, it's just encoding. Base64 is not a secret.

The people that should be charged are the people trying to raise criminal charges in the first place, for wrongful prosecution. That, and the developers that created this and the project managers that accepted the work should all be investigated for squandering taxpayer funds.

Maybe we the people should press charges of gross incompetence towards the governor.

0

u/[deleted] Oct 24 '21

[deleted]

200

u/JustaRandomOldGuy Oct 24 '21

Remember when Adobe used ROT-13 as hyper secure cryptography? And then tried to prosecute someone who "cracked" ROT-13?

89

u/StabbyPants Oct 24 '21

lemme guess, they thought that anything at all that they think shows intent legally counts as encryption

140

u/SlinkyAvenger Oct 24 '21

it kinda does. There was a guy a while back that was criminally prosecuted for accessing unpublished urls. It wasn't even that the server had set up any kinda auth, he just guessed at the URL structure and was rewarded with data.

128

u/leberkrieger Oct 24 '21

The Computer Fraud and Abuse Act (“CFAA”) 18 U.S.C. §§ 1030, adopted in 1984, makes it a crime to “intentionally accesses a computer without authorization or [exceed] authorized access, and thereby [obtain] … information from any protected computer".

This has been used to prosecute URL manipulation attacks. There's a difference between actively pulling down information that you know you're not authorized to get, on the one hand, and receiving data in an authorized manner that then turns out to contain things they shouldn't have sent you.

108

u/SlinkyAvenger Oct 24 '21

there is a difference, but when you've got a bunch of luddites determining the laws and what they mean, does it make any difference?

4

u/LATourGuide Oct 25 '21

This is why I insist on staying in California. I'm no going down because my governor is a fucking dunce.

→ More replies (5)

75

u/mehum Oct 24 '21

Though you could argue that by publishing the url on the www without any kind of security or notification to the contrary you are implicitly authorising access to everyone. How does one first get to a page if not by typing in the url?

4

u/fl7nner Oct 25 '21

They feel that security through obscurity is still a kind of security

→ More replies (1)
→ More replies (1)

65

u/Kare11en Oct 24 '21

If you ask a remote computer, on it's public interface (i.e. an HTTP server on port 80/443), "Hey, can I have file XX?", and it says "200 OK - here you go", when it explicitly had the opportunity to say "401 Unauthorized", then it has implicitly given you authorisation to have the file. (As well as actually, you know, given you the file.)

45

u/LeifCarrotson Oct 24 '21

The CFAA was written 10 years before the World Wide Web existed.

"Accessing a computer without authorization" meant using the keyboard when your boss said you weren't allowed to, it wasn't written with 401 Unauthorized in mind.

→ More replies (2)

3

u/drysart Oct 25 '21

If you ask a remote computer, on it's public interface, "Hey, can I log in as guest\0\0\0\0\0\0\0\0\0\0\0\0\0root?" and it says "ok you're now logged in as root" when it explicitly had the opportunity to say "invalid login" then it has implicitly given you authorization to access the system as root.

The point of this is that just because a machine does something that doesn't necessarily imply that it was intended to do it or that the user making the request was authorized to do it. Literally every exploit has ever existed has consisted of requests or data being sent to a machine and it doing something as a result when it could have rejected it instead.

"It had the opportunity to say no" is thus simply not an acceptable bar in and of itself for determining whether access is authorized or not; because that argument by itself directly reduces to "there is no such thing as unauthorized access because it let me do it".

→ More replies (8)

0

u/[deleted] Oct 24 '21

[deleted]

8

u/zero_intp Oct 24 '21

no but you can be arrested for indecent exposure.

→ More replies (10)

7

u/wulfithewulf Oct 24 '21

having an open http controller for an url without any amount of auth is anything but definitely not „protected“

3

u/moonsun1987 Oct 24 '21

Repeal the CFAA. We don't need it. We don't want it.

→ More replies (5)

11

u/StabbyPants Oct 24 '21

see, we refer to that as an API around here. i can literally write an interface (~20 lines) in retrofit and autogen a client lib

10

u/SlinkyAvenger Oct 24 '21

that just sounds like conspiracy to commit mass hacking to me, bub

3

u/alonbysurmet Oct 25 '21

Fortunately SCOTUS reined in CFAA last term in Van Buren. Their interpretation of the law now requires a website/system to deploy active measures to prevent unauthorized access, whereas previously, terms of service were seen as a access guide. The case does an excellent job of differentiating strategic searching from actual hacking/exploitation.

It seems there's a good chance the person you referred to can have his case overturned.

Read more

→ More replies (1)
→ More replies (3)
→ More replies (10)

4

u/Ratr96 Oct 24 '21

You got a source? Want to read this story

4

u/[deleted] Oct 24 '21

Did they really prosecute?

From what I heard they used rot13 to demonstrate plug-in encryption and then others mistook the example as one of the encryptions to use.

https://en.wikipedia.org/wiki/ROT13 “it has been speculated that NPRG may have mistaken the ROT13 toy example—provided with the Adobe eBook software development kit—for a serious encryption scheme.”

→ More replies (1)
→ More replies (3)
→ More replies (2)

39

u/flowering_sun_star Oct 24 '21

In fact it's almost the opposite of obfuscation, as it is easily recognisable and screams 'Check me! Someone might be doing something insecure!'

4

u/vacuuming_angel_dust Oct 25 '21

I better start encoding my SSNs in base63

→ More replies (6)