Reuters Accused Of Hacking For Typing In URL 569
Aexia writes "Intentia International, a company in Sweden, is suing Reuters for publishing an earnings report posted on their website prior to its official release. The catch? The report couldn't be accessed through 'normal channels', you had to know, or guess, what address to type in order to retrieve it. The precedent this case sets will be interesting. If you don't use a hyperlink on a website, are you committing a crime? You can also read Intentia's take on the situation."
Stating the obvious (Score:5, Insightful)
Stupidity (Score:5, Insightful)
"Reuters News Agency Broke into Intentia's IT Systems"
I would not call it breaking in to surf on someones homesite.
"there was an unauthorized entry via an IP-address belonging to Reuters"
What do they mean, do I have to call them and ask for permission before accessing files publically available on their homesite?
As Reuters didn't steal anything, but simply pointed at on open window (that they found) I would have to say that their act was not illegal. What they should investigate is their internal safety policies, because they need a revision or two (IMHO).
Silly (Score:2, Insightful)
Nothing to do with links. (Score:4, Insightful)
It's not about the existence (or not) of the link, but the source of the URL. While I don't agree with it, I think what they are saying is that if a site doesn't publish a URL (usually through a link, but could be in print, etc) it is not public information and accessing it is unauthorised access. This is the same attitude (if not specific issue) that has a problem with deep-linking [slashdot.org] too.
that's cold man. (Score:2, Insightful)
However, it depends upon what you do with this so-called unpublished material.
What Reuters did exposed the company to a situation before they were ready. Seems to me like the company should have taken more adequate security such as using htaccess passwords, etc.
I court I hope Reuters don't get busted for accessing the information, but for publishing details about it. After all I'm sure that the company in question had a copyright notice on all their pages, right?
There are technical solutions (Score:5, Insightful)
If the publishers of the resource wanted to limit access to the resource they could add authentication, referer checking, or a timestamp check - anything, really. Since they did not, I fail to see how they can have a case.
"Security through obscurity", like having a non-linked but available resource, is self delusion.
if Intentia prevails, it would be very bad (Score:5, Insightful)
In some areas of law, it's unavoidable drawing fuzzy boundaries and considering intent. However, in this case, anybody who wants to protect their information on the web easily can, using standard web access control schemes; they don't need to rely on using obscure URLs. Let's not burden the courts with this.
This is part of a more general and disturbing trend, where lazy system admins don't spend the time set up their systems correctly, or management hires incompetent and cheap staff, and then try to use the court system and police (i.e., taxpayer money) to make up for their own shortcomings.
Mantra (Score:5, Insightful)
If you don't want people to read something, don't put it on the Internet.
of course not (Score:2, Insightful)
And if your server is set to list directories, then it's already "serving" away all of it's pretty little files without much prodding (funny, how a server...serves...files).
http://www.intentia.com/w2000.nsf/pages/PR_5BBD
" The investigation has shown that there was an unauthorized entry via an IP-address belonging to Reuters. The entry took place at 12:51 pm on October 24th 2002, prior to the publication of the interim report for the third quarter of 2002. At approximately 12:57 pm, Reuters published the first news flash giving information on Intentia's third quarter result, without prior confirmation from the Company..."The incident has severely damaged confidence in us as individuals and in Intentia as a company," says Björn Algkvist, CEO of Intentia International AB.
"We question the methods used by Reuters, and our judgement is that we cannot rule out the possibility of illegal actions. As a consequence we will file criminal charges regarding the incident," says Björn Algkvist.
"We will disclose to the Stockholm Stock Exchange all technical details on how the intrusion was made, which will allow them to share this information with other listed companies, so that actions preventing similar events in the future can be made," concludes Björn Algkvist. "
Tip for the Swedes over there at Intentia International:
"chmod --help" -or-
"mv --help"
If an unauthorized page isn't met with a 404 or 403, you did somehting wrong.
url's are like phone numbers (Score:5, Insightful)
The company homepage, www.corp.com, is like the main switchboard number, say 555-1000.
URL's reachable through the home page (www.corp.com/foo/bar) are like internal extensions you can find through the voice menu system (555-1357).
The link with the earnings report is like an extension (555-2468) not on the voice menu, that came off somebody's business card or answering machine or some unknown channel.
That's it. Reuters is being sued over something very much like calling an unlisted direct phone number inside some company. How they got the phone number is, well, irrelevant. They're a news organization, they have reporters, whose job is digging up info like phone numbers.
Deep linking works the same way for anyone else too, of course. Like duh, if you don't want something to be reachable without going through the switchboard, don't give it a direct number exposed to the outside world.
Definition... and metaphorical example... (Score:3, Insightful)
Mod parent up (Score:1, Insightful)
Look! A snake! (Score:5, Insightful)
I'm going outside, right now, with copies of some of my own financial statements.
I'm going to throw them onto the Main Street sidewalk, and stand just near enough to the pile that I can serve hastily-drawn lawsuit papers to anyone who dares to look.
The documents are undeniably my property, after all. Nobody has the right to see them unless I erect a big fucking sign pointing them out, even if they are scattered about a public walkway.
[Moral for the sarcasm-impaired: If you don't want your information to be public knowledge, now or ever, don't let it be publicly available. At all.]
Re:As the adage goes (Score:2, Insightful)
In the news-business it's allways about speed. Beeing the first one bringing the news. Getting authorised the rights to publish something thats allready on the web would seem like a waste of time in any case in this business.
If I found a page on the net, which seemed relevant to my news-page, I'd link it and not check if it's ok. It's allready on the web, right?
And anyone clueless enough to put sensitive documents accessable to the public should suffer the consequences. Maybe he'll learn.
unlisted numbers (Score:3, Insightful)
Krikey. I just don't know where they find people this stupid. Same goes for this deep linking crap. Maybe people should have to pass some sort of test before they get to use the Internet. Otherwise the have to use AOL until they at least understand that anything you post to the web could be publically accessible.
Re:that's cold man. (Score:4, Insightful)
Which is precisely what you'd expect them to do, Reuters being a press agency and all.
I court I hope Reuters don't get busted for accessing the information, but for publishing details about it.
Damn straight. If it weren't for those goddamned financial journalists, I bet Enron would still be trading today. The freedom of the press has got no business interfering with our right to earn a dishonest dollar.
After all I'm sure that the company in question had a copyright notice on all their pages, right?
So what? Do you really believe Reuters breached their copyright in the report?
Get a jar of glue, man.
Re:Stating the obvious (Score:5, Insightful)
The problem with your analogy is that they didn't even use a lock and key. Their doors were open for business and now they are getting mad that someone came in before they could put up the big neon "OPEN" sign.
email i sent the webmaster and investor relations: (Score:2, Insightful)
To:
Subject: Re: Lawsuit @ http://www.intentia.com/w2000.nsf/pages/PR_5BBD3A
If an unauthorized page isn't met with a 404 or 403, you did somehting wrong. You have an incompetent webmaster. The proper way to remove a book from the library isn't to remove the card catalog, it's to remove the book.
-erik-
Intentia's mission statement ... (Score:4, Insightful)
Which roughly translates to: 'we want to use the internet securely'.
They then put some confidential information on their public website, and sue the first people to read it
Re:There are technical solutions (Score:4, Insightful)
That's one of those mantras that get repeated until people believe they're true.
Fact is, all security is obscurity. Security rests on the notion of a shared secret. Some key that both you and the other guy know.
In my opinion, any HTTP GET request is exactly that, a request. "May I have that resource, Server Sir?".
So if I add a login header, is that just another GET request? It's the difference between http://root:12345@www.0wn3d.com/ and http://www.0wn3d.com/.
Or what if I add an obscure folder name to the URL like sf908h234ff98hs9f?
You might argue that the actual crime was in obtaining the password, and I agree that (for example) fraudulently claiming to be an employee (psychological hacking) is criminal, but it's a seperate offense.
That's why breaking into someone's house is "breaking & entry." Even if you don't have to break in, entering is still criminal.
The problem with "ah well, these guys were just poking around, the publishers should have used proper security" is that it raises the bar of what security is to what we experts think it ought to be. Many people don't have the capability to employ such measures, so we're denying them legal recourse.
It would cause the same kind of division in society as if we had a law that said burglary doesn't count unless you have an expensive security system.
Re:Stupidity (Score:4, Insightful)
Once this information was in the puiblic domain then I think their best policy would have been to do nothing, perhaps just issue the information with the best spin they could.
Taking them to court seems like a REALLY BAD idea.
The Web is not a magazine!! (Score:5, Insightful)
All these companies seem to think that the Web is like a magazine: their neat little layout is all anyone should be allowed to use. But they forget that the Web was intentially designed to facilitate deep linking and URL-typing for the purpose of transparent information exchange. They don't get to decide the layout and presentation of the data once they publish it so that it is accessible through an URL.
There is nothing about implicit permission to view here. I assert that they are EXPLICITLY granting permission to any and all to view the document when they publish it via a non-password protected URL.
That is the very foundation of the Web...without it we have interactive television.
Re:Stating the obvious (Score:5, Insightful)
People walking by in the street can not be charged with peeping if they see you walking naked in youre house. Not even if they have to turn their heads to do it. Simply claiming that since you are doing it in youre own house you are supposed to have privacy is not valid. You have to draw the curtains for the expectancy of privacy to be granted.
Now the question is, did they have the curtains drawn. I personally think not. It will be intressting to see what the law has to say about it.
Re:Related: what about referer logs (Score:4, Insightful)
While I'd normally agree, if its protected by some kind of protection (htaccess) - even if its really weak, accessing in would be cracking, same as if a door in a house is open, you still cant nick the TV.
Of course in this case google would have spidered the report before long and they cant prosecute an automatic robot can they?
better analogy (Score:2, Insightful)
The correct analogy is the free information handout kiosk. Somebody put somthing at the Kiosk sooner then they meant to, but behind a different handout.
Completely disagree - form is the key... (Score:4, Insightful)
I completely disagree.
From what I gather from the posts on here, it seems that these guys have a webserver with little to no security on it. If you use a basic webcrawling program, it likely jumps from link to link, which is what we expect AOL users to do online. However, a good web crawler will also check the directory by default as well, to see if there is an index (I've seen some of this in MY referrer logs).
Given that this was sensitive data, it should have been protected. Claiming that it was by not publishing the URL is like sticking it in a window of a building with thousands of windows. Eventually someone may see it.
Your analogy of the credit card numbers would be valid IF they had swiped a password to get to that point. But the server didn't ask for authorisation by any means. It was happy with a basic URL. There's nothing ultra-special about the URL to suggest that it's attempting to be hidden either. I doubt the location was intended to change, but to just be linked to.
Basically, Reuters has provided good reporting using the skills available to anyone with a decent wewbcrawler who has a set list of websites to follow. And if they didn't get it that way but got it through an anonymous tip, that's classic reporting.
Re:Raises some interesting ideas (Score:5, Insightful)
Dumbass:But your honor, that man has stolen a hundred dollars from me! I think I made a reasonable attempt to hide it by keeping it in an old shoe in a hedge at the local park. Who would think to look there?
Re:analogies (Score:2, Insightful)
A public web server is a publically accessable location, if you give out your "private" documents without access control, no matter how obscure your filing system, then you have no expectation of privacy.
How about another example:
I place an unmaned, unguarded, unlocked filing cabinet in times square. This filing cabinet contains information that I encourage members of the public to access. My bank account pin is stored in this filing cabinent under (SKGAKYG@&^KJH). Do I have any right to expect my bank pin to remain private? Does it matter if the filing cabinet is in a publically accessable area of my company? I would say no and no.
Re:Ridiculous! (Score:1, Insightful)
Re:Related: what about referer logs (Score:5, Insightful)
Other possibilities? (Score:3, Insightful)
While it may not be illegal to actually view and read this information, its potentially creating a conflict of interest for investors. If this was an earnings report published before its intended publication date, people will trade off that information. This could create a situation similar to insider trading.
And regardless of this, if it is proved that Reuters did this intentionally, they are totally at fault. They know this information affects the markets, and that the information gives their clients a (potentially unfair) competitive advantage.
If Intentia had an obvious Earnings Report or financial press release procedure, Reuters should know they will potentially be held responsible for releasing false information.
What if this wasn't the final Earnings Report? Than Reuters would potentially affect the trading of Intentia stock based on false information...
Re:Stating the obvious (Score:1, Insightful)
Note: this post wasn't mean for being read. If you've read it nonetheless, prepare to be sued.
Re:Related: what about referer logs (Score:2, Insightful)
Flawed Analogy (Score:1, Insightful)
Except a public webserver is nowhere near a private property. The page was put on a webserver in order to be published.
The best quote from Intentia's website (Score:5, Insightful)
Yeah - no shit Sven, IT blunders with sensitive information tend to do that.
But hey, just to make sure that everyone's confidence in your company is shattered, why don't you do the American thing and file a 'It can't possibly be my fault' lawsuit.
Re:Double standards? (Score:2, Insightful)
Re:Related: what about referer logs (Score:2, Insightful)
No, but I'm allowed to see in your house if you leave the curtains/blinds open.
Re:Raises some interesting ideas (Score:4, Insightful)
Except (to streach the anology to its limits), a public web server is like putting a sign on your garden gate saying "Open to the public".
Public viewing (Score:3, Insightful)
Re:Stating the obvious (Score:3, Insightful)
A web site is not a store. A web site is like the window of a store.
If you go and look at the window and see something half hidden in a corner, something that was not supposed to be left seen to all, at least not yet, you shouldn't be blamed.
If the shop owner doesn't want you to see it, it lets it in the storage room.
'nuf said.
Re:There are technical solutions (Score:3, Insightful)
There are a couple of points being argued in these threads. You make a good one: it is a request, but it has undesirable side effects.
I would say that, legally, this situation could be viewed as some sort of cold caller. You may be offered a free holiday, or you may be offered an investment. Here, "you" is the web server. You get asked for your name, some information about you (content pages), etc, which you're happy to give.
Now you get asked if you want a free holiday. That's okay. You get the holiday, subject to terms and conditions you don't like, but there was no criminal misrepresentation. But what if you get offered an investment, which happens to be a pyramid scheme? Its offered as a sound investment, but its not -- that is fraud.
I would liken your example to fraud: it is a deliberate and malicious attempt to use a request/offer in a damaging way.
The original example (Reuters), however, is a more difficult case. In some ways its like asking someone what they earn, or what their social security number is, or their credit card number. Asking is not illegal, and if they give you the information you have obtained it legally. However, the manner in which you USE that information may be illegal! Having been given information does NOT give you the right to (re)publish it.
As such I would argue that what Reuters did is not hacking. They did not bypass any protection mechanism, they just asked intelligent questions. On the other hand, using such information may have been illegal (I don't know how they made use of it).
Re:Related: what about referer logs (Score:3, Insightful)
Re:Stating the obvious (Score:2, Insightful)
They published the document by putting it in a directory that the web server could access. They made it available. They took an action to release it.
Re:There are technical solutions (Score:1, Insightful)
Furthermore, it should be noted that the act of putting a document on a webserver inside the publicly accessible part of the file tree is an active measure.
An analogy to the physical world:
Let's say you run a library. It doesn't work like a normal library that lets people browse the shelves themselves, but they can go to a librarian and ask for books. Some books can only be given to people with certain credentials while others are available to the public. Would anyone find it acceptable to get sued for reading a book given to you by the librarian in this context? Probably not.
The only situation in such a context where I as a reader could find it reasonable to accept any liability for accessing any book would be if I had given false credentials for a book with limited access.
If I haven't done that, the fault lies with the librarian or his/her manager for not fulfilling their task properly.
They published it! (Score:2, Insightful)
They published it by putting it into a directory from which the web server could serve up documents. End of story.
The arguments about "but that means burglarly is allowed if you have no security" are completely specious. This has nothing to do with security. Through deliberate action, or even accidentally, they made the document publically available. It's as simple as that.
Re:Stating the obvious (Score:4, Insightful)
He could not. If you put something on a
It has nothing to do with peeping either. There's no 'smaller hole' you have to go through technically in order to obtain the requested document from the server. http://www.company.com/secretreports.html is just as available as http://www.company.com/index.html. Site portals are just yellow pages that help you find those URLs. Am I forbidden to dial a phone number that I didn't find in the phone book?
If you want to protect a secret and assume that something will remain hidden, you need to take
Re:There are technical solutions (Score:5, Insightful)
No. In that case, you're trying to circumvent (by having illegally obtained or by guessing the password) a security measure. (Also see below.)
No. There is a difference between trying to receive information (i.e. trying to have it delivered to me), and trying to actively enter someone else's property. The breaking-in analogy is fundamentally flawed, at least as long as we're not talking about trying to circumvent any security that is installed (e.g. trying to guess passwords -- that would be trying to actively enter).
Also note that houses (and physical locations in general) usually make it quite obvious whether they're supposed to be public or private. All private houses, even if they have no locks or security systems, have an implicit security mechanism: doors. Even if they're unlocked, closed doors tell most people not to enter unless invited by someone opening the door, or by a sign that tells them it's public. Why do you think most stores have doors that allow you to look into the store, that have obvious "open" signs, and that sometimes even open for you automatically? It's a way of telling people that the door is, unlike most other doors, not intended to keep them out.
URLs, however, are all designed the same way, there is no obvious difference between private and public resources. The only way to recognize them as private is to request them and see if a password request will show up. And experience suggests that most URLs are public.
Making it potentially illegal to try an URL will get you into the same legal problems as trying to make a difference between precise links ("deep links") and generic links (links to front pages).
Some of the questions you'd have to answer are:
I am a webmaster myself, and I do agree that there are some requests that are sent with obviously malicious intentions (e.g. requests for cmd.exe etc.). But I am also a web user, and I don't want browsing the web to become a legal risk simply because I know how URLs work and make use of that knowledge. Some web site operators seem to believe that simply because they intended their visitors to behave in a certain way, and didn't provide any means for the users to behave differently, that anything but what they expect you to do should be illegal.
There is a difference between an author telling you that it makes sense to read chapter four of his book before reading chapter five, and an author trying to put you in jail for reading chapter five first anyway.
Re: Related: what about referer logs (Score:5, Insightful)
> While I'd normally agree, if its protected by some kind of protection (htaccess) - even if its really weak, accessing in would be cracking, same as if a door in a house is open, you still cant nick the TV.
No, the correct analogy is "if you stand naked in your doorway you can't complain about everyone seeing your naughties".
Like a badly run library (Score:2, Insightful)
Does not listing a library book in the card catalog mean the book is classified, private information? What if someone released movie to the theaters, but didn't advertise or put the show times in the newspaper?
This is just a silly company wanting laws to cover their idiotic mistakes. It's easy enough to store your unreleased earnings report somewhere besides your live webserver.
Re:It is Lotus Domino... (Score:5, Insightful)
http://www.intentia.com/w2000.nsf/(files)/Inten
The previous quarters reports are also available under
Re:Related: what about referer logs (Score:5, Insightful)
But, wouldn't most search engines also at least try to grab index.html on directories in which they've found other files?
Of course, I doubt that's what happened here. From what I can tell on the "victim" website, Reuters just guessed what the URL for the report would be. Who hasn't done that before, in some way or another (e.g. guessing what a broken URL was supposed to be)?
There's clearly NO access control here, except a shining example of how security through obscurity is NOT security at all.
Xentax
Re:There are technical solutions (Score:3, Insightful)
Some might say that a server is like a house, a proper house has a security system and locks. People are free to stand around on the sidewalk, and have a look at your lawn flamingo's, but they may not try to enter the house unless they have been given specific permission to do so, which would be implied with the giving of the security code and a key to the front door.
I prefer to think of a server as more of candy at someone's desk. Some candy may be sitting in a bowl on the edge of the desk where all may freely partake of it. Other candy may be locked up in their drawer, or failing drawers, at least hidden from view. Unless you've been given specific permission to have candy locked up in someone's drawer, you may not have any. Someone wishing to protect their candy needs to do this. Simly placing a blank sheet of paper over the "protected" candy bowl is *not* sufficient to indicate that you don't want people to partake of that candy.
What that breaks down to is that having an easily guessed URL as the only obscurity to protect sensitive information (eg, http://server/2001-report/ with the sensitive one at http://server/2002-report/) is only a blank sheet of paper, it does not indicate that the information in 2002-report is sensitive. If they wished to protect their information, they should use whatever security means are at their disposal, which you're right, may not include technical know-how, but it *does* include the common sense know-how of at least making the URL http://server/randomstring/.
In my mind, the real issue here is that the "attacked" company failed to sufficiently indicate that the information was sensitive. It's very easy to imagine that Reuters was browsing for the report, couldn't find the link, so did what I myself have done countless times, assume that the information is intended to be public, but that some error has prevented it from being displayed that way (a sheet of paper fell off the shelf on top of the candy bowl), and so simply changed a 2001 to a 2002, and removed the sheet of paper.
Re:Compare to "Peeping Tom" (Score:3, Insightful)
Unproven assumption. Reuters knew the URL it would be posted at, and kept looking at that URL until it appeared. Pecause it appeared on a public web server, they assumed it was published. Wrong, but how were they to know that?
Re:Stating the obvious (Score:5, Insightful)
This company clearly messed up. A news agency got some information (and not by hacking!) and published it. The information wasn't fraudulant. If it was false, it wasn't with a disregard for the truth--after all, it was in a document on the company's website. But the company in question didn't like the fact that the information got out, so they sue the news company.
Forget terrorism and its effect on "free speech and free press" (right now a mostly US-centric concern) the real danger is big budget corporations who have the money and time to spend taking you to court because they didn't like what you had to say. It's scary, folks, and it's not getting any better.
Comment removed (Score:2, Insightful)
Freedom of action on internet. (Score:2, Insightful)
"guessing" that this URL exists and contains what I want. If
it doesnt I move on. Essentially any URL I type in is similiar
to this. Now, www.comics.com cannot put their most confidential
stuff at this page and then sue me for not following links.
(links from where?)
There is no rule that accessing pages that are available to my
web-browser are violation of privacy because the web server is
present exactly for that reason: sharing what you dont want to be private.
The bottom line in this case is very simple. Its _my_ freedom of action
to type in _any_ goddamn URL I want, in _my_ browser.
If some moron in their company doesnt know the difference between
their web-share drive and the company private drive, they need to fire him/her.
The company site quotes: "The incident has severely damaged confidence in us as individuals and in Intentia as a company" and I am amused by this. YES thats perfectly true.
Any company that handles up such a vital information in such a careless manner
DOES NOT deserve much confidence or credibility and they are just proving
themselves that they are morons. But instead of accepting their shortcomings
they are raving like an infant.
I think the key to their charge is the allegation: "The investigation has shown that there was an unauthorized entry via an IP-address belonging to Reuters."
Which pretty much sums it up. Is it illegal to type in any url I want in my browser and
view the contents ? I just hope that the verdict is a slap in their face
and doesnt set any idiotic precedents.
They made it world readable - end of story (Score:3, Insightful)
Re:Related: what about referer logs (Score:2, Insightful)
Re:Stating the obvious (Score:4, Insightful)
The plaintiff did not have the metaphorical curtains drawn. There was no realistic way to know the report was supposed to be hidden. The lack of a hyperlink to that report could mean a million different things--they forgot to add the link, they were publishing the report's URL in meatspace media, the link was in a place the defendant didn't know about, the link was propagated via email (hence not visible on any website), or whatever.
But there's only one good way to tell people to stay away from a given web document--the 403 response code.
The simplest common-sense defense would be to remind the court that the plaintiff's server gave a 200 response code. Defendants asked for a document and plaintiff provided it, where is the tort?
Re:There are technical solutions (Score:3, Insightful)
Hope that all made sense, I am late for class so no time for revision! *runs*
Re:Related: what about referer logs (Score:5, Insightful)
Except that my house isn't a public place.
The report was put in a PUBLIC location. Therefore it's up to them to restrict access. Simply "not telling anyone" isn't restricting access.
The question is, "was it malicious?" (Score:2, Insightful)
True, AC's might exploit a flaw with the server itself while the one in the posted story simply access unlinked content, but how would one explain that to a non-technical user like a typical judge/jury?
Either way, this could turn into a bad, bad precident.
Re:Related: what about referer logs (Score:2, Insightful)
Hence the term "publish to the webserver".
Re:Related: what about referer logs (Score:2, Insightful)
Whether someone finds me in a phone book, gets my number directly from me, gets my number from a friend, or guesses my number, the actual phone call is the same.
These anlogies about open doors are misleading, because it is intuitive to think that one should not simply walk into a stranger's house, even if the door is open.
However, if the open door were to a store in a mall, you would probably not think anything was wrong with just walking right in or even telling others about what you saw inside (or where the store is located). Just because the store wasn't listed in the mall directory doesn't make it illegal.
You are all missing one piece about press releases (Score:1, Insightful)
So what Reuters did was smarmy, if guilty as charged. And the Swedish company didn't file a lawsuit against Reuters themselves, as the writeup claims. They reported the event and a criminal action is now pending, which means it isn't just between the two companies now. It's a government thing. What Sweden can do against a non-Swedish company depends on other, currently unknown (to us) factors.
In short, it's a morals thing. There's lots of things we can do, but we don't because it's wrong, even if technically possible. That's the real missing piece in the analysis: thinking that it's OK to do anything, if you know how and can.
Re:Related: what about referer logs (Score:5, Insightful)
Whine and moan all they want, they still stuck it in a public place. They should have stuck it behind a locked closed door. Then it's secure. If you bust open the door, that would be a crime. Finding something sitting in a public place that's not advertised is not a crime.
Re:Related: what about referer logs (Score:3, Insightful)
Anyone who has a web site probably has unlinked pages hanging around, or directories excluded from indexing with robots.txt. The difference is that most of us are smart enough to realize that those pages aren't private or secure, just out of the way and unlikely to be seen. Intentia apparently has trouble grasping this concept.
If You Don't Want To Get Run Over... (Score:3, Insightful)
...don't play on the interstate.
If you don't want people to see your internal company data, don't put it on the Internet.
Got it boys and girls? Yes? OK, now we can have milk, graham crackers, and naptime.
What URLS did they use? (Score:3, Insightful)
www.my.com/report2000.pdf
www.my.com/report2001.pdf
and the world is waiting for 2002 report, would it really be a surprise when millions try to download www.my.com/report2002.pdf one day before the actual release? Come on, _everybody_ would do that. Perhaps one should sue Intentia for violating some stock exchange rules by not protecting the data.
HTTP is a two-way conversation (Score:1, Insightful)
True. But people from Reuters didn't physically enter Intentia's offices against Intentia's will, and carry away paper documents. That's clearly illegal. What happened doesn't appear to be illegal, to me.
Reuters communicated with an automated system, called a web server. Intentia made this system publicly accessible through a system of computers collectively known as the Internet.
Using the internationally recognized communication language of that system, called HTTP, Reuters then conveyed a request to Intentia's system that Reuters wished to be sent information about Intetia's sales reports. Intentia had configured their automated system to grant that request to anyone who asked. The automated system then sent Reuters the requested information, just as Intentia's administrators had designed it to do. Intentia had the option configuring the system to refuse the request, but configured it instead to grant the request.
There is no evidence to suggest that Reuters misrepresented itself to the system, or tried to take something from the system that Intentia had not configured it to grant. In short, the sole claim of "hacking" rests upon the fact that Intentia didn't expect anyone outside the company to ask for that document. But as far as I know, asking for something isn't a crime.
It's not burglary if you ask the salesperson if they will give you something, and they choose to give it to you.
Disclaimer: I Am Not a Lawyer. I Am Not A Police Officer. I Am Not a Alien from Mars. I am Not a Flying Fish. "Mod Me Down If You Must, But..." Natalie Portman. Hot Grits. All Your Base. Karma. Insert Standard Slashdotism Here.
Score -5, Silly Disclaimer.
--
AC