Some DNS Requests Ruled Illegal in North Dakota

jgreco writes "A judge in North Dakota has just ruled that requesting a zone transfer from a public DNS server is criminal activity within the meaning of the North Dakota Computer Crimes Law. A zone transfer is a simple request that a DNS server hand over information in bulk, and a DNS server may be configured to allow or deny such requests. That the owner of a DNS server would configure the server to allow such requests, and then claim such requests were unauthorized, is simply stunning."

Unbelievable

[Chrisq (894406)]

This in effect means that you cannot set up a secondary DNS server in North Dakota. Any ISPs in the state should probably relocate!

Re:

[BoomerSooner (308737)]

This is typical of most judges I've encountered. They are too lazy to actually understand the information in front of them they are adjudicating. For example, getting divorced. 10k pages of discovery and the judge just flips through it. No understanding of accounting or much of anything else. It's like arguing to a 5th grader about law. 99% goes over their head if it's not criminal related. So beware if you're in any kind of trial where it's a technical field, or hell, even anything with discovery beyond wh

Re:Unbelievable

[billcopc (196330)]

I don't think a judge should be expected to read through 10k pages of vindictive banter in order to decide how to split a marriage. I don't expect them to become an expert in the simple-yet-confusing DNS system either. The important facts should be presented in concise layman's terms.

"Sir, a zone transfer is when you type 'dig google.com axfr'. It is a standard feature of the DNS protocol and software suite. The only way it can be abused is if it is left unprotected by the network administrator, much the same as a house can be abused if you leave your doors and windows unlocked."

J:"I get it. Plaintiff, you're an idiot! Case dismissed."

The fact that these simple truths can be irreversibly concealed through the one-way hash known as legalese, is just evidence that the legal system is broken beyond repair. At least you can brute-force RSA :/

Re:Unbelievable

[Pollardito (781263)]

"Sir, a zone transfer is when you type 'dig google.com axfr'. It is a standard feature of the DNS protocol and software suite. The only way it can be abused is if it is left unprotected by the network administrator, much the same as a house can be abused if you leave your doors and windows unlocked."

if you leave your doors and windows unlocked it's still a crime to "abuse" the house, it almost sounds like you're arguing that zone transferring is trespassing

Re:Your example is wrong

[j-pimp (177072)]

Just because the door is unlocked does not mean you have permission to enter.

Well look at it this way. If I walk into a laundromat and there is no attendant on duty I would not consider myself trespassing. No reasonable person would. I've been to laundromats without attendants on duty. I assume someone opens them up ion the morning, locks them up in the evening and periodically comes buy to refill the vending machines and the like.

If I am a reasonable person on the internet, and a server responds to a zone transfer request, I expect that I am authorized to look at this information,

"Your example is wrong" is wrong.

[roggg (1184871)]

Your DNS server is not your house. It's your store. Yes, it's private and belongs to you, but it has a public interface. People walk into your store when it's unlocked because the door is the public interface, and the lock on the door is how the owner meters or controls access. DNS servers are much the same. They serve up a public interface. Making a DNS request of an open server should be no more illegal than walking into the 7/11. If they don't lock it, how am I supposed to know it's closed?

Re:Unbelievable

[Intron (870560)]

FINDINGS OF FACT

"In all intended uses of a zone transfer, the secondary server is operated by the same party that operates the primary server. A secondary intended purpose for zone transfers is to permit trouble shooting in which case zone transfers may sometimes be undertaken via the manually conducted host -l command. In those instances, however, the person conducting the diagnosis acts with the authorization of the operator of the system and is usually the network administrator for the system."

Sounds like the judge understood it pretty well to me.

Re:Unbelievable

[Sancho (17056)]

Geeks don't like this ruling, though, because it's not black-and-white. A geek think that if it's open on the Internet, it ought to be legal. If it asks for a password and you break in, it ought not be. Absent other means of gaining authorization, a request on the Internet implies a request for authorization, and a reply with the requested information from the server ought to imply authorization. The burden should be on the server operator to restrict or allow access, because on a pseudo-anonymous Internet, there's no other metric we can use. "Most of the time, the server operator wouldn't want this?"

Re:Unbelievable

[orclevegam (940336)]

In this case, the geek in question performed the DNS queries as part of an ongoing investigation into the spam activities of the ISP in question. This was not a case of someone with malicious intent, or even someone exploring for the sake of exploring, this was a computer professional attempting to track the source of some spam and to compile evidence against the spammer. In this regard he was acting more as a PI (I realize a PI is usually licensed by the state, but it's still close enough) in attempting to investigate something that if not directly a crime, is at least questionable.

If I was investigating you, and I came and knocked on your door saying "My car broke down, can I use your phone to call a tow truck?" and while inside your house used a hidden camera to take pictures, this would also be "not authorized", but in most states it's still perfectly legal, and you couldn't then turn around and try to sue me for trespassing.

The reason the judge ruled against the defendant in this case seems to have had a lot less to do with the merit of the case then it did several instances of the defendant giving false testimony, and in at least one case directly violating an order of the court. Essentially the judge was ticked at the guy, and that biased the case against him.

Re:Unbelievable

[Richard_at_work (517087)]

Why the support on Slashdot for anti-spam laws then? If your smtp server accepts my connection and accepts the mail I subsequently send to you through that connection, how is this any different to the arguments posed elsewhere in this thread about public access services and presumed legality?

Re:Unbelievable

[dekemoose (699264)]

if I make a bad analogy but it makes sense to me, is it still a bad analogy?

Re:Unbelievable

[JakusMinimus (49854)]

If I pose a stupid rhetorical question, but it makes me chuckle and/or snicker, is it still a stupid rhetorical question?

Re:Unbelievable

[SanityInAnarchy (655584)]

In all intended uses of a zone transfer,

Well, there's a problem right there. No one person knows all the intended uses of a zone transfer. I learned a new one today from a sibling post -- actually migrating DNS information to a new host, when switching service providers.

the secondary server is operated by the same party that operates the primary server.

*chokes on breakfast* ...what?

I've been using it for almost a year now, for dynamic DNS. It means I get to configure and run a real DNS server, and set it up exactly the way I like, and then, when I need to update the records on my real DNS servers (at zoneedit.com, dyndns.com, etc), I only have to change one setting -- the master host. This means that, for example, if I want to switch to another system, I don't have to learn a new API (or write one to crawl their website) that's much more complicated than a single POST request, updating which master server they should update from.

(Just been reading that zoneedit.com sucks, so I'm considering switching to dyndns.com, which honestly is pretty cheap, and their service which does zone transfers is cheaper than their service which has a web interface.)

That is to say: I operate the primary server, and the secondary and tertiary servers are operated by a third party, even if these secondary and tertiary servers are listed in my domain as primary and secondary servers. This is hardly unique to dynamic DNS -- it's also used in cases where there is a static IP, but you only want to maintain one server, and you (obviously) can't guarantee five nines of uptime on that server. So you pay someone to run a secondary DNS server.

A secondary intended purpose for zone transfers is to permit trouble shooting in which case zone transfers may sometimes be undertaken via the manually conducted host -l command. In those instances, however, the person conducting the diagnosis acts with the authorization of the operator of the system and is usually the network administrator for the system.

That's reasonable, but answer this: If I were to use the "host" command -- just "host", by itself, looking up MX records and such -- should I be worried about it being illegal? What about "whois" and such? There are plenty of times when it's reasonable to expect that a third party should run diagnostics -- such as when the first party is completely clueless, and needs to be told so. [centos.org]

Some other poster put it very clearly -- geeks generally believe that if you make a service public, it is public. It's certainly possible to limit zone transfers to the IP address of the secondary DNS server. This would not be an absolute protection, but it would at least show what the intent was.

This has been debated fairly often with respect to open wireless access points. What you have here is, according to the machine protocols involved, a machine shouting "Look at me! My name is LINKSYS, and I'm open! Just connect if you want to get online!" It is trivially easy, in most cases, to have it instead broadcast "My name is LINKSYS, and you'll need a password to connect!" Or, alternatively, to not brodcast at all -- to just sit in a corner until someone says, "Hey, LINKSYS! Let me connect!"

It's not quite that bad, but it's similar. "Hey, ns1.example.com! Would you mind telling me what all the subdomains of example.com are?" (There are legitimate reasons for doing this, too -- maybe I'm a spider, and I want to find web pages which aren't specifically linked to by www.example.com.) At this point, if ns1.example.com says "Sure! There's mail.example.com, and www.example.com, and, oh yeah, super.secret.stuff.example.com"... how is this your fault? If super.secret.stuff was really that secret, ns1.example.com could've left it out, or could've said "No, sorry, I'm not going to tell you."

The reason geeks w

Re:Unbelievable

[MyLongNickName (822545)]

What is more unbelievable is that you'd take an article summary like this as being the gospel. More often than not, it is someone who hasn't really read the whole article, but wants to see his name on the front page of Slashdot. Dispense with a few facts, create some sensationalism, and the crack Slashdot editing team puts it up without fact checking.

Re:

[ari_j (90255)]

The article isn't much better. I think that it's going to be nothing but sensationalism unless someone gets ahold of the actual court documents.

Re:Unbelievable

[orclevegam (940336)]

There's actually a good deal of information in there if you read between the lines a little. What I gathered from it and one of the sites linked by it, is that this guy is well known in the anti-spammer circles as a spam investigator that can compile loads of detailed info on spammers. Apparently Sierra (the plaintiff) is notorious for spam and also for suing anti-spam activists. During the course of compiling evidence against Sierra, this guy performed a DNS Zone transfer (most likely to prove that the source of some spam was actually a server hosted by Sierra). Sierra then sued him claiming the zone transfer wasn't authorized by them, and therefore it was illegal (not going to argue if that's logical or not, just summarizing here). Up to this point any technically minded person would probably think the plaintiff was on pretty shaky ground. However, the defendant screwed himself over it seems by annoying the judge various ways. According to the findings, the defendant gave false testimony on several occasions. It may or may not have been false testimony, it's sometimes hard to say when lawyers get involved, but the judge perceived it as such and that's what counts. Much worse it seems, is that the judge ordered the defendant not to perform certain scans of Sierras network, but he then proceeded to ignore those orders. This action seems to be the one that really blew the case for him, as it's apparent the judge was really not happy with him for that one.

Re:

[Crazy_CorranH (1207148)]

So if you're in North Dakota and you're reading this, you better run for them thar boondocks, boy. We're coming to git you!

Well, coming from ND, I'd have to say it's all boondocks. Where should I run to now?

Re:Port 53 rebel from hell

[jtroutman (121577)]

I'm guessing you're young, under thirty at least. I only say this because the "the tag may only be removed by the consumer" bit is a change that was made about fifteen years ago, before that they read "Do Not Remove Under Penalty of Law" in bold, black letters. So most people grew up with these ominous tags on all their pillows and mattresses warning that if they removed them there were stiff penalties involved. Nowadays, not so much. Meh.

So who's the nerd now, huh?

consequence of bad computer crime laws

[j0nb0y (107699)]

Most states have computer crime laws that pretty much say this: It is illegal to access a computer that you are not authorized to access.

This basically means that if you don't have written permission to access a computer, you can't access it legally.

So everyone who uses computers breaks the law, and the law is only truly defined by who prosecutors decide to prosecute.

This state of affairs is completely ridiculous, but unless you find a tech savvy Judge, the situation is unlikely to be changed through the courts.

Re:consequence of bad computer crime laws

[mcvos (645701)]

By this reasoning, looking at a website without written permission of the webmaster would be illegal too. The Judge has basically declared the internet illegal.

Re:

[CastrTroy (595695)]

The act of putting up a website (or any other internet server) on the public internet should be enough to say the operator of the server gave you permission to access it. If you don't want people accessing your server, at least put a password on it for basic access control, or if it requires more security, than put it behind a VPN/Firewall box.

Re:

[Simon Brooke (45012)]

The act of putting up a website (or any other internet server) on the public internet should be enough to say the operator of the server gave you permission to access it. If you don't want people accessing your server, at least put a password on it for basic access control, or if it requires more security, than put it behind a VPN/Firewall box.

The act of putting up a DNS server is exactly the same. But we now know it's illegal to access a DNS server, therefore it must be illegal to access a web server.

Without written permission in triplicate, signed in longhand by the owner of the data using a quill pen and attested by the county registrar and the sheriff, of course.

Re:consequence of bad computer crime laws

[Sancho (17056)]

Further reading from the link I posted states that the court isn't ruling on normal DNS requests. Under "CONCLUSIONS OF LAW":

2. The Court need not determine whether a normal, single DNS query is authorized within the meaning of the statute. Even if there had been any authorization for a such a DNS query or lookup, Ritz exceeded that authorization in violation of the statute by conducting a zone transfer and attempting further access.

So the court isn't claiming that a DNS query, in the general case, is illegal.

Re:consequence of bad computer crime laws

[_Spirit (23983)]

I always think it rather silly to state that a judge declared something illegal. Yes I know that he interprets the law. But all the judge does is look at the law and the case. So all the judge has done is show that the law is stupid. The laws that make this illegal were already around. Don't blame the judge, blame the legislators and push to get the law changed!

Re:

[strangel (110237)]

The reason people say that a judge declared something illegal is that in order for there to be consequences in such a case, there must be a trial. A trial will always go through a judge, so a judge always has to interpret the law. Part of this interpretation depends upon past precedent...therefore it is possible that if the next judge isn't bright enough to recognize a bad precedent when he/she sees one, he/she will follow the precedent. This further strengthens the precedent for later cases.

Re:consequence of bad computer crime laws

[morgan_greywolf (835522)]

It IS completely ridiculous. I doubt very much that OSDN or SourceForge (or whatever they're called this week) wants to have to give explicit permission to each and every user on Slashdot, but that's what it appears to have come to because judges are techno-illiterates.

If a service is running on a machine connected to the Internet and that service is obviously not secured, then the only thing that can be assumed is that permission to use that service is implicitly granted, especially in absence of notices stating otherwise.

IOW, if you run a Web server on port 80 and require no authentication, then it can be easily assumed that you intend to publish any materials served via the Web server to the public Internet -- you expect people to access it.

Ditto if you run a DNS service that allows zone transfers to all comers -- you expect that DNS zone transfer will occur and no one will need permission from you to do so.

To rule otherwise is nothing but pure stupidity.

Re:consequence of bad computer crime laws

[aproposofwhat (1019098)]

More to the point, what idiot would put DNS records relating their internal private network on a publically accessible DNS server?

That's what Sierra did, according to the court decision.

Either the admin responsible is incredibly stupid, incredibly lazy or just hasn't thought through the security implications.

Re:consequence of bad computer crime laws

[jvkjvk (102057)]

No, it's not completely ridiculous. We can talk about generalities as long as we want but they are nothing but straw men. This is a specific case, and it appears to be a special case, where the defendant had an injunction against him to prevent him from harassing the company in question.

Essentially, the judge ruled that the injunction did indeed include the DNS servers the company had. Imagine that, he got that one right!

IOW, even if the company was running a web server on port 80 and require no authentication, it can easily be assumed that --- the defendant would still be barred from making requests to that page. No, not people in general one specific individual who was barred from interacting with the company.

To rule otherwise is nothing but pure stupidity.

Re:consequence of bad computer crime laws

[_.- thimk! -._ (898003)]

You might try reading the actual content of the ruling, not just the article.

http://www.spamsuite.com/node/351 [spamsuite.com]

If you had, you would probably at least know that the Judge was a 'she' not a 'he'. If you did actually read the article, this might be a good indicator of how much you actually paid attention to what you were reading...

Several of the 'conclusions of law', as stipulated, are indeed seriously problematic. She did not specify her rulings upon the basis of an injunction. She specified them based upon the actions themselves. THAT is why technically savvy individuals consider her ruling to be badly flawed.

Her conclusions on Zone Transfer Queries, for starters, are seriously flawed. There are plenty of legitimate reasons to make DNS Zone queries when you are not an employee or someone else acting with the explicit permission of the entity who put the server in place. Many ISPs cache entire zones to cut down on excess DNS traffic for requests from their customers, for example.

For another, while it is difficult to say with certainty not knowing the exact details of the testimony of the defense's expert witness, a reading of her response by someone knowledgeable with DNS configuration suggests reasonably that he may have attempted to explain that there are specific methods that would be used to prevent zone transfers to unauthorized servers, that there were other methods that would be used to configure the server to provide zone information in response to external requests, and that by configuring their DNS server in such a way as to give the Zone information, the plaintiffs were authorizing the transfer of information and making the information publicly available. If their DNS server was configured to respond to external Zone Transfer requests, this information would in effect be public, as anyone at all, not just the defendant, who issued a perfectly normal host command would have received that information. If this was not their intent, the issue would be one of incompetence on the part of their technical staff, not one of 'hacking' on the part of the defendant.

Her suggestion that using a command switch for 'host' that is clearly documented to query information that was publicly available constitutes 'unauthorized use of a computer system' is unfounded, overly broad, and, to any technically knowledgeable individual, deplorable. She does not state that she reached her conclusion because of any injunction against the defendant. She states her finding is based upon the facility of the program itself, and her miraculous idea that somehow use of this normal function is somehow mystically, only intended for a specific subset of target users she has imagined. One that is, again, seriously flawed.

'Knowledge available to the average user' should NEVER be used as a yard stick for what constitutes the acceptable bounds of computer use. The 'average user' is ignorant of the actual function and capabilities of their systems to a point that is common to describe them, quite accurately, as largely 'computer illiterate'.

If no one knew more about any particular thing than an 'average' individual does, at any given point in time, we'd still be hunting and gathering. To suggest that this baseline should have anything to do with determination of what constitutes a potential criminal act, if applied to any other circumstance, would immediately render anyone of actual knowledge, rather than vague theories about a subject a criminal.

What do you know, for example, about repairing the engine of your car. Say you know quite a bit about it. Should you be considered a criminal if you make repairs on it, based upon knowledge you have, if you aren't a certified mechanic? How about if you repair your mother's car with that knowledge. Does that make you a criminal? By this Judge's logic, it would.

If you don't like that analogy, try this one. Let's say that the 'average person' knows that telephone bo

Re:consequence of bad computer crime laws

[kalirion (728907)]

Be glad he didn't tase you, bro.

DNS illegal now? Read again.

[by Anonymous Coward]

Might want to read the actual court ruling instead of the populistic and alarmist comments surrounding it. As I read it, the defendant already had been told by the court to stop bothering the plaintiff, and he then proceeded to ignore that. In and of itself the ruling doesn't outlaw dns requests, altough the judge's grasp of the technology clearly could stand improvement.

Re:DNS illegal now? Read again.

[tgd (2822)]

See this is why we need a (-1 Informative) moderation... because clearly from the tone of the post and the the majority of the replies, rational response is not the goal of this story submission.

Re:DNS illegal now? Read again.

[autocracy (192714)]

TFA really sucks. The linked judgment is much more useful to read. I'm kind of saddened by the judges focus on "zone transfers," but it's clear that the issue is not about zone transfers. The issue is a pattern of malicious activity that the defendant had an injunction placed on him for. He violated that injunction. It was corporate cyber-stalking harassment, really. I'd say that the zone transfer was illegal in context, especially with an outstanding injunction to stay off the company's servers.

Facts from the ruling

[InvisiBill (706958)]

18. Ritz was not an authoritative name server, a DNS server, nor any kind of computer at the time he accessed Sierra's computer.

I'm pretty sure that one wins some sort of award reserved for the highest level of intellectuals.

21. The information which Ritz published was not public. Moreover, much of the information was not publicly accessible.

In all seriousness, I think this is where the major issue lies. The judge ruled that because most people don't know about host -l, that the information was private, even though it was publicly available with a standard command.

If Ritz had previously been ordered to leave Sierra alone, and hadn't, then that's a basis for the ruling right there, completely ignoring any aspect of DNS. From the court documents, the guy sounds like quite a piehole.

Re:Facts from the ruling

[squiggleslash (241428)]

Well, the ruling's more like being told that you can't enter a shop that happens to have a door unlocked at the front after you've repeatedly entered it and been told explicitly to go away because the shop's not open yet.

Re:

[onecheapgeek (964280)]

From the ruling:
7. Ritz, at all times material, acted intentionally and with the intent to gather as much DNS and other information as possible about Sierra and its principals, agents and related entities and persons. Ritz made the information he gathered available to several persons, including a competitor of Sierra, SuperNews and SuperNews accessed that information. Ritz has admitted that SuperNews personnel accessed the zilla queries file where it resided on his computer via http connection.

8. The intend

Re:DNS illegal now? Read again.

[squiggleslash (241428)]

What's absolutely hilarious about this are the number of replies to this article complaining about "clueless" Judges who "don't understand the issues" and aren't prepared to "read the evidence" right in front of them. Uh-hum. Because all you guys did, right?

Oops

[slarrg (931336)]

I didn't mean for anyone to read this post on the internet. So it illegal.

Re:Oops

[mulvane (692631)]

Damn YOU!!!!

I try to be a somewhat law abiding citizen. Thanks for my first criminal act of the day I didn't even mean to commit.

Turn computer crime laws upside down

[unlametheweak (1102159)]

From TFA:

"The Court rejects the test for "authorization" articulated by defendant's expert, Lawrence Baldwin. To find all access "authorized" which is successful would essentially turn the computer crime laws of this country upside down."

One could only hope.

FUD

[Telephone Sanitizer (989116)]

It's a civil case.

The worst that can be said about it is that it's bad precedent and the judgment was wrong.

The judge did not make DNS requests illegal.

Public information?

[suso (153703)]

Asking a public internet server for public information that it is configured to provide upon demand?

This quote from the article is debatable and the reason why its not a good idea to allow zone transfers. A lot of times, information that you would rather not be public is in zone files. I've seen a some people put processor information in HINFO records. This is bad because there was a cryptographer in the 90s that discovered that its possible to determine random number generation sequences based on your processor model and frequency. So it wouldn't be good for that info to be public.

Its not a good idea to allow zone transfers. Although its useful when an ISP that you are transfering a zone from doesn't want to give you all the zone records.

How would he obtain permission to access it?

[Rogerborg (306625)]

He can't email them, because clearly that's zomg h4xx0rz1ng their email server.

an old proverb

[tylersaurus (1221772)]

Those who can: write code. Those who can't: write laws.

Can you imagine if every politician in the house and senate knew how to program? Granted a good portion of them would still be writing awful spaghetti code... but for the most part at least they would not be able to compile it.

Computer systems vs human systems

[mlwmohawk (801821)]

What I find interesting is that "computer systems" i.e. networks, disk drives, files, etc. ae well understood by us computer folk. What is "obvious" to us has come from a lot of experience and learning. More over, in constructing things like the internet, we develop a lot of "rules" that make sense within this context.

In the non-nerd world, a lot of the rules created by us nerds run afoul of what most people expect. DNS is a perfect example. To us, it is MADE to serve data. If you put data into DNS, you've made it public. To the rest of the world, however, that doesn't make sense. Its the same issue with HTTP. We see putting stuff on a web site as making it public, but non-nerds see things like deep linking a violation of their site because it does not promote the interaction they expect (viewing ads etc.) and have invested in. To them, you are circumventing their revenue model.

I'm not 100% sure we're 100% right. I don't think we are wrong in our views, but I see the gray area between the two.

Re:

[pla (258480)]

I'm not 100% sure we're 100% right

Since we made the whole damned ball of wax for our own amusement, and Joe Public decided to tag along for the free porn, I'd have to say that yes, only the geek interpretation matters. Joe can thank us (as can the Hunters of Commerce who hungrily stalk Joe and his kind), but his "interpretations" of the scenario simply do not matter.

If you don't understand the rules of poker and try to play, you'll go home shirtless. The same idea applies here. If they want into our

Re:Computer systems vs human systems

[cyxxon (773198)]

Well, yes, you are right with what you wrote, but you basically forget the IMO most important angle: "we techies" invented this shit so that it gets used the way we want it. "They" only hopped on, and actually built e.g. their websites in "our" realm. Then, all of a sudden, they realize that our realnm has some consequences that they didn't foresee (for failure to understand the concept, or most often just simply for failure to try to do so), and begin to sue and badmouth those that are leftovers from the original phase, or those that adhere to the original philosphy.

In this case (ignoring the fact that the defendant already had an injunction against him) the operators could probably have prevented their DNS server to serve this data (probably, as I am not an admin in this area). In other cases, such as deep linking, well, it is a little rougher, but they could for example not use frames, but good page layout, which automatically shows all their ads in the standard headers and such, or make stuff password protected, or use .htaccess to redirect requests that go straight for their meat back to the frontpage, just like many free image hosters do now for hotlinking. But no, they just decide to litigate...

Best. Ruling. EVER!

[InfinityWpi (175421)]

Why the hell aren't we celebrating this, people? Okay, for DNS, it sucks... but look at it this way...

It doesn't matter if you set up your system to 'automaticly' share the files you just downloaded... people who accessed them did so without authorization. It can't be considered 'sharing' if you didn't authorize people to download them from you... could this ruling be a tool agaisnt the MAFIAA?

A human analogy

[oz1cz (535384)]

I can lock my house, but even if I do not do so, you will still be trespassing if you enter my house.

Re:Why am I not suprised?

[plover (150551)]

That's not at all true. The judges I've had dealings with have been damn smart people.

What you're forgetting is that in most court cases, the defendant is there for one of two possible reasons: they really weren't responsible, or they were responsible but are now lying about it. And the plaintiff or complainant is there to make sure something "legal" happens in their favor, and they're not above lying to get their desired outcome, either. Usually there's a lot of both. That means the judges are professionally sitting at the mouth of a never ending river of bullshit, and they have to keep control of the situation.

It's not that judges can't or refuse to understand the technology; it's that the cases are about the people, which is where their focus must remain. The computer didn't act of its own accord. It operated under the direction of its owner. The question of "was there malicious intent?" has nothing to do with DNS or any other logic-based technology and everything to do with the two guys standing in the courtroom.