TorrentSpy Must Preserve Data In RAM For MPAA 489
Transient writes "Reaffirming a magistrate's earlier decision, a federal judge has ordered TorrentSpy to begin keeping server logs as it defends itself against an MPAA lawsuit. In her opinion, Judge Florence-Marie Cooper interpreted federal discovery rules broadly. ' Judge Cooper took issue with TorrentSpy's argument that data in RAM is not "stored." She noted RAM's function as primary storage and that the storage of data in RAM — even if not permanently archived — makes it electronically stored information governed by federal discovery rules.' Given that TorrentSpy has limited access for users in the US, the ruling may be moot. But it does set a precedent for other, similar cases. 'Under this interpretation, any data stored in RAM could be subject to a subpoena, as at a basic level it is a "medium from which information can be obtained" just like a hard drive. '"
so hand them a stick of RAM (Score:5, Funny)
hehe (Score:5, Funny)
Wait, what?! (Score:5, Funny)
I guess it's time to buy stock in storage companies. I wonder if this also applies to cache RAM? There could be an infinite loop in there somewhere...
Re:so hand them a stick of RAM (Score:5, Funny)
Re:Need more disk space now? (Score:5, Funny)
C coding standards need a rewrite (Score:2, Funny)
free command: illegal under the dmcaa
memory leaks: standard operating procedure
dangling pointers: stool pigeons
Comment removed (Score:5, Funny)
Re:What I want to know... (Score:2, Funny)
Bah, move the servers offshore. (Score:3, Funny)
The reason? The broker in question is one of the few who has not yet fled to the free market of international waters. They kept their servers in the US. Lesson 1. Globalism is not just for the big boys. In fact its friendlier for little players. You, me, mom and pop downtown, we're all the ones who should incorporate abroad if we do it at all.
Lesson 2. Torrentspy should work actively with friends from abroad, preferably from some nordic country or some place not friendly to the gestapo tactics of the EU, and US, China, etc. Right now, for the time being, South America seems allright, as would a drilling platform in the middle of the ocean (or close to shore, your preference). If you choose such a path and have money, hire good security, if you don't then you'd best be a good shot, and a great swimmer, you may need to defend such a place, especially if you declare it a separate independent nation or sovereign territory. After that, with a policy of neutrality and free trade with ALL who come to you, there is a fairly good chance you may even draw some of the Linux "community" to you, especially those who seek a place to host that is not "restricted" by either the East or the West.
Re:so hand them a stick of RAM (Score:5, Funny)
That sounds like a job for SELinux. Lock the system down so hard it doesn't allow root logins at all, and logins under the id that the servers are running under. Have all that become enabled, say, five minutes after boot, or that it starts enabled and must be disabled from the boot command line during boot.
Make sure the system responds with an error message that explains all this if you try to login as one of the protected accounts...that to login you have to reboot the server.
Re:Whoops! (Score:3, Funny)
Re:Wait, what?! (Score:3, Funny)
"Sir I direct your attention to page 0x1A86FB2 of the memory dump. Do you or do you not recognize writing the bits 101100011010111101?"
Re:Soo.... (Score:5, Funny)
The cost of paper may build up to something considerable after the first couple seconds...
Re:If I understand correctly... (Score:2, Funny)
Just as long as you don't cross them.
(sorry, had to)
Re:Soo.... (Score:2, Funny)
This Just In (Score:5, Funny)
RAM log (Score:5, Funny)
2007.08.28 15:40 set bit 1243434
2007.08.28 15:40 set bit 1243435
2007.08.28 15:40 cleared bit 1243436
2007.08.28 15:40 set bit 1243437
Obviously guilty!
Re:Soo.... (Score:2, Funny)
Re:What I want to know... (Score:3, Funny)
Simple answer - The MPAA asked for it (no doubt doing their best not to burst out laughing), describing it as absolutely critical to making their case, with probably a snipe about how those damned pirates would try to get out of it by claiming they couldn't realistically get to it.
As for the suitable means to archive it, we don't really need to ask that here on Slashdot, because we already know the answer - You can't, in practice. In theory, you could set up a system with some sort of virtual memory transaction log, but it would run so slowly as to make subpoena-ing its contents irrelevant ("well, after a two week boot time, we've finally gotten to the login screen. We expect to have a shell session by Saturday...").
Re:Bah, move the servers offshore. (Score:3, Funny)
Re:Soo.... (Score:3, Funny)
Re:Soo.... (Score:3, Funny)
Re:Whoops! (Score:3, Funny)
Re:Typical (Score:2, Funny)
Slashdot's always been like that, though...
Re:Soo.... (Score:3, Funny)
man mem (Score:1, Funny)
Re:Evidence destruction ? (Score:5, Funny)
It's impossible to say because your seven line program contains at least one bug. (I'm assuming that the presented program is C and not some imaginary language).
Firstly, although you've correctly specified that main() should return an "int" you are actually returning a value of "size_t" which may or may not be defined as "int", depending on the platform. Secondly, you haven't checked the return value of fgets(). On error, fgets() returns NULL. This isn't necessarily the same as the nul character so depending on the platform, strlen() may fail (possibly even catastrophically on certain machines, such as the DeathStation 5000).
You've used the strlen() function without including its proper header.
Lastly, although this isn't really an error but it does demonstrate your inexperience, you have enclosed "buf" in parenthesis in the sizeof expression. Remember, sizeof is an operator not a function. The only reason you would ever use parenthesis in conjunction with sizeof is if you were asking for the size of a datatype. For example "sizeof(int)" or "sizeof(*char)". Using parenthesis any other time would be equivalent to expressing a simple sum as "(1) + (2) == (3)". Not incorrect, but pointless.
A more correct program might be...
Remember, C isn't for amateurs. That's why high-level languages were invented. To demonstrate how difficult it is to effectively program in C, I've deliberately left a bug in of my own as well as a potentially confusing design issue. See if you can find them.
every highschool student knows (Score:2, Funny)
that depends entirely on the font and the size of the font being used
Re:Bah, move the servers offshore. (Score:5, Funny)
Re:Bah, move the servers offshore. (Score:2, Funny)
Re:Hippie FUD (Score:4, Funny)
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on
I will not make funny comments on