Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

And what law would you use to target someone who wrote some code and posted it for free on the internet that was willingly consumed?


The computer abuse and fraud act? Seems like a pretty easy question to answer.


Maybe I'm miss understanding things, but it seems like anyone can publish an exploit on the internet without being a crime. In the same way encryption is free speech.

It would seem unlikely this guy would be also logging into peoples boxes after this.

It seems a much tougher job to link something like this to an intentional unauthorized access.

At this point, we have no confirmed access via compromise.

Do you know of a specific case where the existence of a backdoor has been prosecuted without a compromise?

Who would have standing to bring this case? Anyone with a vulnerable machine? Someone with a known unauthorized access. Other maintainers of the repo?

IANAL but it is unclear that a provable crime has been committed here


> IANAL

Best to leave it at that.

It's not worth your time or the reader's time trying to come up with a technicality to make it perfectly legal to do something we know little about, other than it's extremely dangerous.

Law isn't code, you gotta violate some pretty bedrock principles to pull off something like this and get away with it.

Yes, if you were just a security researcher experimenting on GitHub, it's common sense you should get away with it*, and yes, it's hard to define a logical proof that ensnares this person, and not the researcher.

* and yes, we can come up with another hypothetical where the security researcher shouldn't get away with it. Hypotheticals all the way down.


I think this thread is talking at cross-purposes.

1. It should be legal to develop or host pen-testing/cracking/fuzzing/security software that can break other software or break into systems. It should be illegal to _use_ the software to gain _unauthorised_ access to others' systems. (e.g. it's legal to create or own lockpicks and use them on your own locks, or locks you've been given permission to pick. It's not legal to gain unauthorised access _using_ lockpicks)

2. It should be illegal to develop malware that _automatically_ gains unauthorised access to systems (trojans, viruses, etc.). However, it should be legal to maintain an archive of malware, limiting access to vetted researchers, so that it can be studied, reverse-engineered and combatted. (e.g. it's illegal to develop or spread a bioweapon, but it's ok for authorised people to maintain samples of a bioweapon in order to provide antidotes or discover what properties it has)

3. What happened today: It should be illegal to intentionally undermine the security of a project by making bad-faith contributions to it that misrepresent what they do... even if you're a security researcher. It could only possibly be allowed done if an agreement was reached in advance with the project leaders to allow such intentional weakness-probing, with a plan to reveal the deception and treachery.

Remember when university researchers tried to find if LKML submissions could be gamed? They didn't tell the Linux kernel maintainers they were doing that. When the Linux kernel maintainers found out, they banned the entire university from making contributions and removed everything they'd done.

https://lkml.org/lkml/2021/4/21/454

https://arstechnica.com/gadgets/2021/04/linux-kernel-team-re...


Talking at cross-purposes?

No, people being polite and avoiding the more direct answer that'd make people feel bad.

The rest of us understand that intuitively, and that it is already the case, so pretending there was some need to work through it, at best, validates a misconception for one individual.

Less important, as it's mere annoyance rather than infohazard: it's wildly off-topic. Legal hypotheticals where a security researcher released "rm -rf *" on GitHub and ended up in legal trouble is 5 steps downfield even in this situation, and it is a completely different situation. Doubly so when everyone has to "IANAL" through the hypotheticals.


I'm not looking for a loophole or a legal hypothetical, I'm wondering if our laws are keeping up, which they very often do not with tech.

This is not unauthorized access, but is also clearly wrong. I'm wondering if its illegal, or if its unauthorized access . . .


And of course an attacker like this has a high likelihood of being a state actor, comfortably secure in their native jurisdiction.


> but it seems like anyone can publish an exploit on the internet without being a crime

Of course. The mere publishing of the exploit is not the criminal part. Its the manner & intent in which it was published that is the problem.

> At this point, we have no confirmed access via compromise.

While i don't know the specifics for this particular law, generally it doesn't matter what you actually did. What is relavent is what you tried to do. Lack of success doesn't make you innocent.

> Who would have standing to bring this case?

The state obviously. This is a criminal matter not a civil one. You don't even need the victim's consent to bring a case.

[IANAL]


Some types of criminal cases are only pursued on a victim's complaint.


Not this kind!

See for example page 35 in the Justice Department’s computer crimes handbook (dated, but basically AIUI the same way they still do things) [0]

[0] https://www.justice.gov/d9/criminal-ccips/legacy/2015/01/14/...


By this logic you could say that leaving a poisoned can of food in a public pantry is not a crime because poison is legal for academic purposes, and whoever ate it took it willingly.

Also, I think getting malicious code into a repo counts as a compromise in and of itself.


Or shooting someone isn't a crime, since you only pulled the trigger. After all it was the bullet that killed them


Similar laws we use to prosecute someone who intentionally brought a poisened cake to the potluck.


Are you suggesting intent is impossible to determine?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: