Judge Orders TorrentSpy to Turn Over RAM
virgil_disgr4ce writes "In an impressive example of the gap of understanding between legal officials and technology, U.S. Magistrate Judge Jacqueline Chooljian 'found that a computer server's RAM, or random-access memory, is a tangible document that can be stored and must be turned over in a lawsuit.' ZDNet, among others, reports on the ruling and its potential for invasion of privacy."
Take the chips out of the machine and send them to the other side.
"Please sir, hand over your motherdisk."
Maybe she meant 'hard drive'? The majority of the people I supported while working IT during college used the terms RAM and hard drive interchangeably.
-gb
And these guys get arrested for destruction of evidence when they find that the RAM is blank. Un-freaking-believable.
They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
You are correct, so the only viable solution is to remove the RAM with out turning off the machine!
-Rick
PS: KIDDING!!!
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
Here is a working link to the article: http://news.zdnet.com/2100-9588_22-6190900.html
It should be Law that legal officials of all sort have to have a "qualified technical advisor" present when giving any court order or summons. Mind you we geeks would then lose our main advantage when it comes to skating on the fringes of laws *cough"mp3 collection"cough*.
I am Jack's complete lack of surprise. -Fight Club
I wonder if its floppy or hard ram?
Reminds me of the Seinfeld episode where George wants to keep his high score in a Frogger arcade machine and rigs up a car battery so he can unplug it and move it elsewhere.
At night I drink myself to sleep and pretend I don't care that you're not here with me
Sure, I'll unplug it and send it to you right away, your Honor!
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
As the TFA explains, the judge means that the RAM would become a legal document, and that any information put on it would have to be retained for later examination, and that if this ruling were extended to things like SOX, a SOX-complying company would have to keep transaction logs or images of their RAM so that the state of the RAM at any point in the past could be accounted. EEep.
Don't blame me, I voted for Baltar.
Keep in mind this is a magistrate judge, which is one step below a trial court judge (who is already generally below 2 levels of appeals courts). Magistrate judges work on a very fact-specific level, so I don't think this ruling would make even persuasive authority. I think I cited a magistrate judge like once, and that was just because the subject was so obscure I couldn't find anything else...
Do some googling. This Slashdot bit doesn't adequately explain it.
Torrentspy has been ordered to retain records of all of the information that is in their RAM as part of discovery. Not turn the physical RAM chips over to the court.
Even if they had the information off the ram, there's no way to tell what context they're running the information in.
1001011010100100 - Well with this information I have no choice but to rule the defendant innocent... oh wait...
1001011010100101!! That changes everything! - I have no choice but to rule the defendant guilty !
Well, back to rejecting software patent applications.
Damn! I knew we should have stopped referring to 'pages' of memory.
No incumbents, not no where, not no how.
Vote them out every term.
Even if they could prove you went to torrentspy...theres nothing they can do......even if they proved you downloaded a torrent...there is nothing they can do, as torrents have no copyrighted data.....tey would have to prove you downloaded the content the torrent pointed to, which at that point is out of the torrent spy loop...but who know what they'll try to say
In a world of acronyms, the words are the real victims.
oh please let it be so... that would show just how ridiculous it is... the sheer amount of disk space and processor cycles required to effectively record the state of RAM for enterprise servers would bring this whole stupid ruling crashing down...
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
Wholly agree. Another implication in the article is that someone could hit you with a court order, and the moment you were served, if your machine was on, turning it off (or even killing a process or doing something that caused a pageout) could be destruction of evidence.
Don't blame me, I voted for Baltar.
It has nothing to do with handing over physical ram. It's about whether you have a piece of information in memory but deliberately fail to ever write it to a log - and whether you can be compelled to add that to your logs.
The more worrying demonstration of ignorance for me is:
"To imagine my information being disseminated without my written or verbal consent is unnerving," she said. "Then again, if I'm doing something I know is illegal, can I protest?"
If you smoke dope in your own home, can you protest if the police break in without any kind of a warrant?
If you like oral sex in any of the states that ban it, can you protest that your landlord installed a hidden video camera to catch it?
If you had depression and were hospitalized for being potentially suicidal, can you protest if the hospital gives the information to a former spouse who's trying to get child custody?
Of course you can damn well protest. Violation of your privacy is not acceptable simply because you're happening to commit a crime at the time.
It's especially not acceptable if you're not even necessarily committing a crime (seizing all server logs of all people using a torrent when only some of them are sharing copyrighted information over it). "Many people in group X are criminals, thus we're pulling all information on group X" is absolutely not acceptable. Imagine if the argument was "Many people in this housing project are involved with drugs. So we're demanding complete phone taps for everyone that lives there and we'll decide who's a criminal once we have that."
he still couldn't understand this udderly basic principle
Moo.
There are 0x40000000 types of people: those who understand 32-bit IEEE 754 floating point, and those who don't.
The meatspace equivalent to RAM-recording is to require conversations to be taped and those tapes to be produced. Worse (more intrusive) actually, since RAM must be slowed to be recorded. RAM is as ephemeral as air.
I expect an appeal. I understand the desireability and value of the evidence, but rules are rules.
ZDNet appears to be forwarding referred clicks (possibly just from Slashdot) to the .comnull address. It works fine if you just paste in the link and press Enter.
You can never go home again... but I guess you can shop there.
Since all we have is her decision in the case, I'd have to assume that the in court arguments made it around to the fact that TorrentSpy isn't logging connections to their server therefore the logs requested by the MPAA do not exist. The MPAA probably made the argument that the data did indeed exist (it appears the location they chose was in RAM), but it just wasn't being captured.
The order is far closer to an order to maintain logs than it is a request to pull the RAM out of the server and mail in. But being dramatic about how stupidly stupid the MPAA is and Judges and everybody but Slashdot geeks is much more fun than actually reading and understanding a court order.
What is most worrisome about the ruling, if everyone would shut up about physical RAM chips, is that a transient collection of 1s and 0s is considered a 'document'.
"Sacrifice for the good of The State" - The State
At every point in our technical development, the most functional machines are always compared to humans. Now, the closest machine that can emulate actions similar to our own is the mini(personal) computer and connected devices. This analogy will continue, as machines get more and more functional.
For purely technical reasons, we have a convention now that a person's thoughts are private. We have no technical way of reading a person's active thoughts or dreams trolling their memories. We have different levels of social responsibility for a person's thoughts and actions.
Aside from the technical issues of volatility, this issue is central to what information is public and what information is private. Taking a copy of a computer's RAM, which is technically possible in a running computer using, say and external hard drive, by order of a court, is a very real possibility, and one that has extremely deep implications for what information society deems as "discoverable".
I think the real issue here - the one that would be fascinating to discuss - is for senescent beings (and computers are marching that way closer and closer), is there a line that we should not cross and allow other beings (humans, computers when we agree they are sentient) to have truly private thoughts? According to the mentality of this ruling, no any information you can grab is fair game. It bodes very poorly for future generations with highly advanced MRI devices that can read thoughts.
When I was a kid, RAM was made of flip-flops and I had to go to school with three feet of snow, and it was uphill both ways. Oh boy.
Nowadays, BosstonesOwn (794949), RAM is made out of capacitors and they have to be "refreshed", that is, some circuit re-reads/re-writes the same values all over many times per second. One second without refresh, and all the data is gone for ever and ever and ever.
BEFORE: a flip flop has an input, a clock, and an output. when you put 0 in the input and pulse the clock once, the output is now 0; if you put 1 in the input and pulse the clock, the output now has 1. This is how one bit of memory is stored. Also know as SRAM, this kind of memory is fairly large in terms of integrated circuits (like 20 transistors in-die), is reasonably fast, and it's still found in L0/1/2 caches of microprocessors, in quantities in the range of Megabytes.
NOW: you have a capacitor, if you put 1 in its input (that is the same pin as its output) it retains this one for a fixed period of time (T). if no-one tries to read this bit in, like, T/2, a circuit in the memory reads this bit, and if it's 1, writes again 1 in its input. Also known as DRAM, this kind of ram is smaller per-bit (one capacitor in-die, 40-60 times smaller than a bit of SRAM), but the memory itself has to add in the end the size of the refreshing circuit, it's slower (because read cycles must be synched in time with refresh cycles), and is found in the "RAM" socket of your motherboard, in quantities in the range from hundreds of Megabytes to Gigabytes.
So, DRAM _really_ clears, i.e., if unplugged when plugged again it's all beautifully zeroed.
Ok??
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
The problem the judge has in this case is perception. The plaintiff's are arguing that there is a way for the defendant to create a tangible record of the contents of their RAM which the defendant is obligated to produce under the rules of evidence. The defendant, in trying to educate the judge as to the nature of RAM is perceived as hiding something. The judge is forced either through her own ignorance or through defense council's incompetence to order the production of the information. It's unfortunate, but probably the correct decision if the judged thought that the defendant was hiding discoverable information. Thankfully there is an appeal and perhaps the appellate attorneys will be more competent or the judge will be more open receptive.
We willna be fooled again!
While industry experts lamented the judges decision in this case, this newest revelation, that computer RAM should be turned over as part of discovery, proves that she has no concept of the issues she is addressing in her court. This provides fertile grounds for appeals as she is obviously dealing with issues she cannot even comprehend.
The fact that she has ordered the defendant to CREATE evidence (log files), in order to turn it over to the plaintiff as part of their discovery request is absurd.
Good security is based upon reality and common sense. Common sense is a function of having common knowledge.
The judge didn't get the technical aspects wrong. The judge did not take technical aspects into account at all, since it's a legal decision. The finding was that the contents of a computer's memory - specifically, the persistence of a client's IP in the network stack or server software while transmitting data - was relevant to the case and it should be provided to the court. In other words, TorrentSpy's loophole of not logging anything to disk is not valid and is no different legally from creating and then deleting logfiles. Once that decision has been made, the technical aspect is someone else's problem (TorrentSpy's).
(IANAL)
The real "Libtards" are the Libertarians!
I am sure that there will be a lot of "snicker" replies -- how can the magistrate be so stupid...
But this is an interesting idea. RAM holds information, specifically the IP addresses in this case.
"Sorry, we don't have the IP address available; they are never recorded". To which the reply is: "They ARE recorded. In RAM. So copy RAM".
Why this is a useful result: It means that it *could* become illegal to build a computer that has "unreadable" memory, because *that* memory may be where information needed by a court is being kept, and it needs copying.
Which means that "secure writeable storage" for DRM becomes illegal (at least on computers).
But, back to the topic, the magistrate is dead on. Of course, the RAM could simply be dumped onto a hard disks, lather, rinse, repeat. I don't think INTERPRETATION of the document was discussed!
Just another "Cubible(sic) Joe" 2 17 3061
Courts are trying force administrators of systems that do not log activities to start keeping logs.
There are many problems with this:
Technical: RAM contents are not permanently stored due to the technical nature of RAM. This judge wants to change that.....essentially storing everything that passes through RAM.
Cost: Why should the owners and operators of systems bear the cost of copyright enforcement? As a system administrator, what do I gain by spending my company's money on lots of disk and tape to keep logs for the RIAA? Why is that my responsibility?
Responsible party: If my users agree to only use my systems for legal purposes and they break that agreement, why am I required to provide anything to any third party? If they violate my TOS, I should be able to kick them off my network. The RIAA and their civil case should not involve me or my network. Their gripe is with the end user. If they need my help to pursue their case, then they don't have much of a case.
SARBOX forces companies to keep all emails and IM records as potential evidence. What's next? Recording every spoken word just in case someone needs it in court?
The burden of proof should be on the accuser - not on the accused.
-ted
don't hard drives have cache memory? Better record that too, just to be safe!
Read again, the argument is that the contents of RAM are effectively a document, and the order is to retain that document instead of discard it.
Sounds reasonable to me, even if technically impractical (you can't realistically store every change to memory).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
They failed to make that case & I doubt they could.
Whilst ephemeral, data is being captured in RAM - to maintain a session of course they've to identify the IP. It isn't really all that hard to write that data to disk. Ok the logfiles would be a few GB a day - from technical viewpoint the judge's request is reasonable.
The SonicBlue / ReplayTV case in 2002 involved an order by the court to ReplayTV to create the technology to record information about subscribers for purposes of determining how much usage was violating the TOS and the law.
From the defendant's brief in that case, which makes it quite clear that the information does not exist and would involve an affirmative duty to surveil:
Federal Rule 34 Neither Requires Nor Authorizes An Order To Create Records That Do Not Exist.
Not surprisingly, Plaintiffs cite no authority for such an order. It is well settled that a party is not required to create, either in paper or electronic form, data that does not currently exist within its possession. Steil v. Humana Kansas City, Inc., 197 F.R.D. 445, 448 (D. Kan. 2000) (party "cannot be compelled to produce documents which do not exist" ). Rule 34 "only requires a party to produce documents that are already in existence." Alexander v. Federal Bureau of Investigation, 194 F.R.D. 305, 310 (D.D.C. 2000) (emphasis added). "A party is not required 'to prepare, or cause to be prepared,' new documents solely for their production." Id. Plaintiffs misunderstand Rule 34 and the law relating to the discovery of data compilations. It is true that Defendants may be required to produce both hard copy documents, and electronic data, that are stored in Defendants' own files and computers. But, with the sole exception of the limited my.ReplayTV.com information discussed below, the information sought by Plaintiffs is not "electronically stored" on Defendants' computers. It does not exist anywhere yet. It does not even exist on individual consumers' PVR hard drives, much less on Defendants' computers. And if the information is created, and a program written to log it in the future, it would exist on a consumer's personal property, not on ReplayTV's computers.
Rather, Plaintiffs are asking the Court to order Defendants first to write a program to implant in a consumer's ReplayTV unit in order to create and store the data, and then to write software to collect the data from consumers (without further notice to them) and disclose it to Plaintiffs. Neither Rule 34 nor case law obliges Defendants to take these extraordinary steps.
--originally provided by Mike Godwin in SonicBlue discussion, Cyberia-L
a r b o r l a w -- legal blog for entrepreneurs and small business
Exactly like that, except, you are told that your house could have been, is, or could be a crime scene, so you are required to take one photo of every room every, say, 10 seconds and produce them up to 7 years later if so asked. Say you have 10 rooms in your house, when you do the math that's about 220 million photographs you must take at your time and cost and produce for the court. It's no big deal, it's just a "snapshot" so that the information isn't lost over time...
Learn to love Alaska
You have been misinformed if you take the slashdot summary at face value.
And you have been misinformed if you RTFA.
The judge's decisions responds to most of the comments posted here, and the lawyers comments naively repeated by the author of the article.
Instead, read the decision (RTFD) that the article links to.
Although she mistakenly says websites have RAM, she definitely knows what RAM is, if you read her analysis about why the RAM should be turned over. She doesn't want the chip, she wants the ip address that temporarily pass through the website server's RAM.
Based on existing case law from other copyright cases, whatever passes through a computer's RAM is a tangible copy, if only a temporarily one. According to the rules of discovery, the defendant must produce this copy because it is within their control. It is within their control due to the fact their provider uses the a web server (Microsoft's), and this server has the capability of logging ip address that temporarily pass through the computers RAM.
So "turning over the RAM" actually means "hand over the documents that are temporarily stored in the RAM by simply turning on the logging function of the webserver." The judge is simply following existing case law and discovery procedures.
While I object to some of the conclusions that the court has drawn in this particular case, I am far more concerned with the broader implications of the paragraph starting line 20 of page 24, referring to the the US Wiretap Act (18 U.S.C. 2510-22). "First, the court concludes that this statute is not implicated because, as to electronic communications, it only prohibits interceptions during transmission (not while in electronic storage, i.e. RAM), and the disclosure of electronic communications intercepted during transmission. See Konop v. Hawaiian Airlines, Inc.302 F.3d 868, 878-879 (9th Cir. 2002). This is true even though storage is a necessary incident to transmission." This is an explicit writ authorizing anyone the legal right to record any and all information that passes through the RAM on their computer. I.E. if I own webserver X, I am within my legal right to log all information, or a portion thereof, that passes through my system, by virtue that it will reside, however briefly, in that system's RAM. This includes data for which my server is not the intended recipient, as it has still been electronically stored on my system. For example, I could record the addresses of all emails that route through my server. And since this recording is my property, my consequent sale of said information to interested third parties is completely legal. This also means that any gov't agency that so desires this information can acquire it via a straightforward civil information discovery request, bypassing the more stringent requirements to obtain a valid wiretap warrant. The implications of this ruling for the future of data protection and security are frightening. While I am confident that it will be overturned or at least limited in the future, the potential for abuse is mind-boggling (like most things governments seems to do these days).
What's next, being ordered to "log" the electrical signals on your phone line?
The files are inside the computer!
I've read recently (was it on /.?) that in order for 4th amendment protections to apply, there has to be a reasonable expectation of privacy.
When you send unencrypted bit streams over equipment that is owned by a third party, you have no reasonable expectation of privacy.
If you want to create a reasonable expectation of privacy, use a privacy envelope of some sort. E.g., PGP. Otherwise, the email you send has even less legal protection than snail mail. AS IT SHOULD BE.
Not in modern DRAM. Modern DRAM is basically [sic] a capacitor.
Sure, forgetting about the whole row and column stuff, and the sense amps...
However, due to the natural resistance of silicon there is always some leakage current leaving the capacitors.
Incorrect. Capacitors lose charge because dielectrics are not perfect insulators, and thus some current actually leaks through from one plate to the other.
This means that RAM left alone for more than a few tenths of a milisecond will lose enough voltage to drop to a logical 0
Disturbingly wrong. Most manufacturers specify that a row of DRAM must be refreshed at least every 64 milliseconds. In fact, Wikipedia cites a pdf saying that some information can be retained for up to minutes in a cell of DRAM - though you will get some bit errors.
TO prevent this, RAM is constantly refreshed- the ram chip will spend spare cycles writing its own value to itself.
Actually, the memory controller will issue a refresh command to the DRAM chip. This is probably what you were thinking about before...a row refresh must happen every 7.8 microseconds or so (depending on the RAM chip). But, that's because the refresh operation only refreshes a single row. The DRAM chip usually has an internal address counter, so you just say "refresh the next row" and the DRAM chip already knows what the "next row" is, and afterwards it increments it so the next time you issue the refresh command, it refreshes the next row. If you execute these refresh operations every 7.8 microseconds, then in 64 milliseconds you will refresh every row of memory on the DRAM chip.
Oh, and by the way, reading from any cell of DRAM will refresh the entire row that cell is on, because reading from DRAM is a destructive operation. Therefore, there's actually a row of latches at the bottom of the columns, and the values from those latches are placed back into the capacitors while the bit of interest is being shuffled out onto memory bus.
Writing to a cell also requires reading the entire row, which means that writing also refreshes that row.
:(){
SRAM only consumes "large currents" (for ambiguous definitions of large) whenever it needs to switch states.
DRAM, however, consumes "large currents" every time it charges a row of capacitors. However, the large current is very brief (on the order of several ns) but happens frequently and periodically (on the order of several us).
DRAM is smaller, simpler and power hungry BECAUSE of all the refresh's required.
Er, it's power hungry because of the refreshes, but it's smaller because it's 1 capacitor and 1 transistor, as opposed to several transistors.
As far as simpler....I wouldn't go that far. SRAM is WAY simpler to interface to than DRAM, because the SRAM doesn't need an intelligent memory controller which understands how to burst large amounts of data, and how to handle the latency for the first access. Oh, yeah, and don't forget that the memory controller needs to send refresh commands periodically to the DRAM...
:(){
Ah, sorry about that, it was something completely different...
..... they won't believe you.
-----
FIRST JUDGE: Aye, very passable, that, very passable bit of copypasta.
SECOND JUDGE: Nothing like a nice order of Château de RAM, eh, Josiah?
THIRD JUDGE: You're right there, Obadiah.
FOURTH JUDGE: Who'd have thought thirty year ago we'd all be sittin' here with Château de RAM, eh?
FIRST JUDGE: In them days we was glad to have the price of a cup bits.
SECOND JUDGE: A cup o' all zeroes, at that.
FOURTH JUDGE: Without capacitors or electricity.
THIRD JUDGE: Or bits.
FIRST JUDGE: In a cracked cup, an' all.
FOURTH JUDGE: Oh, we never had a cup. We used to carry our RAM in a rolled up newspaper.
SECOND JUDGE: The best we could manage was to suck on a piece of damp SIMM.
THIRD JUDGE: But you know, we were happy in those days, though we were poor.
FIRST JUDGE: Because we were poor. My old Prof used to say to me, "Money doesn't buy you happiness, son".
FOURTH JUDGE: Aye, 'e was right.
FIRST JUDGE: Aye, 'e was.
FOURTH JUDGE: I was happier then and I had nothin'. We used to scavenge for bits in this tiny old hall with no ventilation for all the excess heat from the computer cluster.
SECOND JUDGE: A hall! You were lucky to work in a house! We used to have court sessions in one dark room, all twenty-six of us, no furniture, 'alf the memory modules were missing, and we were all 'uddled together in one corner for fear of stepping on one them SIMMs.
THIRD JUDGE: Eh, you were lucky to have a room! We used to have to chew wires for random bits in t' corridor!
FIRST JUDGE: Oh, we used to dream of workin' in a corridor! Would ha' been a palace to us. We used to get our RAM from an old water tank on a rubbish tip. We got woke up every morning by having a load of IP lawyers dumped all over us! House? Huh.
FOURTH JUDGE: Well, when I say 'house' it was only a hole in the ground covered by a sheet of tarpaulin, but it was a house to us.
SECOND JUDGE: We were evicted from our 'ole in the ground; we 'ad to go to the lake and see if someone had simulated a Turing machine with rocks.
THIRD JUDGE: You were lucky to have a lake! There were a hundred and fifty of us working in a computer case in t' middle o' road.
FIRST JUDGE: A tower case?
THIRD JUDGE: Aye.
FIRST JUDGE: You were lucky. We worked for three months in a mini tower in a septic tank. We used to have to get up at six in the morning, ziplock all the zeroes, eat a crust of stale bread, work pro bono, fourteen hours a day, week-in week-out, for sixpence a week, and when we got home the DOJ cronies would thrash us to sleep wi' a belt.
SECOND JUDGE: Luxury. We used to have to get out of the lake at six o'clock in the morning, clean the lake, eat a handful of 'ot gravel and simulate a Turing machine with our intestines, work twenty hour day pro bono for tuppence a month, come home, and DOJ would send people to thrash us to sleep with a broken bottle, if we were lucky!
THIRD JUDGE: Well, of course, we had it tough. We used to 'ave to get up out of pizza boz-sized case at twelve o'clock at night and lick road clean wit' tongue just in case someone had left some bits there. We only ever found two bits, a one and a half a zero, worked twenty-four hours a day pro bono for sixpence every four years, and when we got home our DOJ had already fired us and would send someone to slice us in two wit' bread knife.
FOURTH JUDGE: Right. I had to get up in the morning at ten o'clock at night half an hour before I went to bed, drink a cup of sulphuric acid, work twenty-nine hours a day for RIAA, and pay the recording industry for permission to come to work, and when we got home, Gonzales would kill us and dance about on our graves singing Hallelujah.
FIRST JUDGE: And you try and tell the young people of today that
ALL: They won't!
My other SIG is a Sauer.
DejaView.. It would take snapshots of your ram and create a file off them so you could restore them later and umm *cough* bypass copy protection.
Cool little product.
---- Booth was a patriot ----
And send the MPAA the bill for a new laser printer, toner and about a thousand reams of paper, and first class postage for shipping it to them.
Rerun this command as often as the printer finishes, (and get more ram *evil grin*)
T
Laws are horrible moral guides, moral guides make even worse laws.
i am kinda late to the fray, but the actual ruling doesn't seem to concern itself with the technical aspects of RAM, instead, it addressess the argument "does TorrentSpy have electronic recordings of their server logs", and, as far as read, it seems to say "yes, because data is in RAM for a while, and RAM is an electronic media built for the purpose of storage and retrieval of information, albeit short-term one, and TorrentSpy can read the data during that time".
The whole argument is there in the first place because TorrentSpy seem to allege they don't have logs because the logs are not on disk, but in RAM, which is transient and not an electronic medium.
So, to my IANAL eyes the ruling says "if you are in the US, and you have been issued a court order to store all your electronic communications, you better do so and don't come up with excuses which are lame technically."
I respectfully decline to comment on whether this ruling is good, bad or ugly.
You did, in fact, just positively smack the shit out of that n00b. Well done.
Why bother.
Q: Does the judge really want TorrentSpy to hand over their RAM chips?
A: No, f****** moron. The judge simply says that information that exists in RAM can be retrieved.
Q: What's this all about?
A: It goes down like this:
1. TorrentSpy has been slapped with an order to log traffic
2. TorrentSpy claims that since their servers have no hard drive (only RAM) there "are no logs"
3. Judge calls bullshit. The logs exist and can be transferred to other media. TorrentSpy must do this cause they are legally obligated to do so.
As usual, the article summary misrepresents the story. TorrentSpy claims that it can't turn over certain data because it was never logged. The judge ruled that since the data in question existed in the RAM, TorrentSpy was in possession of said data and must preserve it for discovery, i.e. start logging it. The judge in no way ruled that they must physically turn over the RAM chips.
Q: But a defendant cannot be compelled to create new documents for the plaintiff, even if the new document would just be a compilation and/or summary of other documents.
A: That's just it: the information allready exist. It just need to be stored "permanently" (read: for years instead of miliseconds).
Q: Wouldn't this mean that TorrentSpy has to change the HW configuration of their servers?
A: Yes, It basically means that using RAM-based servers without permanently logging traffic is not the legal loophole once believed.
This is not the first time that a company/organization has been ordered to change the way their system works. In the SonicBlue/ReplayTV case [2002] the court ordered ReplayTV to create the technology to record information about subscribers for purposes of determining how much of ReplayTV usage was violating and the law.
Q: Is there no way out of this? Will the MAFIAA have their way?
A: The judge doesn't say that the logs have to be stored electronically... Nor that they have to be stored chronologically or otherwise in a logical, searchable manner.
SIG: TAKE OFF EVERY 'CAPTAIN'!!
This is the most stupid headline I've seen on Slashdot for as long as I've been here. The summary isn't doing much to clear things up either.
People, read the damn article! But I guess an easy chance to get your post moderated Funny is too hard to give up a lot of you. Too bad there is basically only one joke in this entire thread and it's been told about 200 times now.
Seriously to whoever posted this submit better summaries!