Genuine source :)

http://www.cafepress.com/oppluvvpigg

there was this thing called cheating that oink and the mods spent plenty of time trying to prevent. to do this you have to adjust what your client tells the tracker. in other words there is no proof that these logs contain accurate information. they could easily be tampered with by oink himself or the users. for example, i’ve saw a guy in the forums one time that had a ratio of 10000.00 in a matter of minutes of being on the site. he was obviously kicked off, but there is no proof that this type of thing did not take place regularly.

now quit fucking crying. jeez

I bet 90% of ex oink users would not use a public “oink”

so then what? No good content and public “oink” is shit just like every other public tracker

In a few decades you’ll be like todays old war guys who actually wet their pants but brag about how heroic they were when they were young and in war… you’ll be Grandpa Simpson (not that I think war is heroic).

Todays copyright laws are outdated and not fit for an internet-world bending over like a girl won’t help changing that.

Seems unfair that all oinkers could potentially get lumped in the same category of pirates trying to take down the industry which isnt the case at all.

Thanks to oink i’ve bought way more albums, discovered way more bands, went to way more shows and spread the word about all these new bands to friends than i ever would have without it.

It’s a shame they don’t take the oink model and make it a legit site. That’s all we really need.

really.

well i’m convinced!

Must be very easy to assuage your fears by portraying the authorities as the villains of the piece and therefore dull witted morons.

Unfortuantely police computer teams aren’t stupid.

logging IP addresses

logging torrents downloaded

logging torrents uploaded

As far as I remember, oink did all three of those. They have to log IPs so they can ban cheaters, right? And I’m pretty sure I saw the IP address I was using (my neighbor’s wireless) in my profile (with an “only visible to you” notice, but still recorded in there.)

They also had a list of torrents you snatched, as well as what you uploaded.[/quote]

Actually, just because it displays the IP you are logged in from doesn’t indicate it’s being stored. In fact, Paine himself indicated that they didn’t log IPs for snatches in his blog. (http://tehpaine.blogspot.com/) Check the quote below.

[quote=Paine]A few people have asked me if we logged the IP you snatched things from. The answer is no, we did not log snatch IPs.[/quote]

So, yeah.[/quote]
Wouldn’t that be entrapment?[/quote]
It says so in the blog, wow it must be true!

I mean thse people are honest enough to do something they know is legally extremely risky *irresective of how noble people might find it). These guys were engaged in illegal activity and you are just going to trust something they could have easily said to cover their own backsides.

I for one would like a damn site more evidence than just ‘trust us, we’re professionals’.

Yeah, professionals who got stalked and caught with their pants down.

Quote:
Originally Posted by ……. View Post
“For the record, from Paine’s blog:
Edit 2: This is an important one — Your passwords do NOT need to be changed, they were stored as salted MD5 hashes. All the authorities have is the hashes. The only way they can get the original passwords is via brute force. The chances of that are slim to none if you followed standard good password practice.”

A:
Only if you follow good password procedure. If your password is kitten, it’s likely to be broken in under 30 seconds.
The problem occurs because although password hashes are salted with a ’secret’ key, the secret is stored alongside the hash. The MD5 hash of [secret]password[secret] is no harder to break in brute force than the MD5 of password, when you know what [secret] is. Because MD5 hashes are so quickly generated, if you used any regular word for your password a good dictionary attack will find it in seconds.

The thing that should give people hope is that nothing found on the server can in anyway be used in a real case against any members. It is impossible to say whether a user with certain stats listed in the database shared even one copyright file, or that they uploaded the amount listed in the database.
They may have filenames from the snatched table, but without having the exact file that was shared, the name of a file is not enough. I could share a file called starwars that was actually midget clown porn. Without a copy of that file, nobody can say it definately was or wasn’t starwars that was shared.

All the talk of hunting down members is just BS on the part of the record industry, and they know it.

“Hate to rain on the feelgood parade, but a couple of points.

Quote:
Originally Posted by GoodOmens View Post
An interesting tibit dug up on torrentfreak:

a source has stated that the OiNK membership list was not only encrypted, but also equipped with a ’self-destruct’ type mechanism which relied on a regular signal to continue in ‘OFF’ mode.

Should be comforting to all the users^^
That source doesn’t know too much about encryption.
If the entire table was encrypted, the server would need a copy of the decryption key (in public/private keypair encryption) or another method for decrypting the contents in order to operate. A webserver cannot perform magic and call up details without decrypting. The police have the server which means they have the decryption key/method and it’ll take no time to get the plain text.

The self wiping database may be true, and may not be. The problem with requiring a regular ’signal’ comes when there are problems on either end that result in the signal not arriving. Leaseweb have had their share of problems lately, with something like 50-60% packet loss in one of their datacenters. The loss of signal would cause a downtime and loss of some stats as the site would have to be rolled back to a backup database. If that has never happened, it’s unlikely to be true.

Even if it is true, you have to consider data forensic methodology. When dealing with HDDs for evidentiary purposes, you never work on the HDD in the original machine. You never even boot from that HDD.
What the police teams will be doing is taking a copy of that drive before they do anything, then browsing the files with the drive attached as a non-booting slave. No cron jobs will run to wipe the database, no code will be running awaiting the ’signal’, and all MySQL databases are copyable as files.
All they have to do is copy all the files from that HDD to a clean MySQL install and they can read everything at will.

The only thing that could save the data from being examined is if the users table was stored in a HEAP table (stored in memory). Even then, some data may have been written to disk as the table expands outside of memory allocation or is operated on with large join operations that would exceed available memory. In either case, data may be recoverable from disk.
It’s unlikely the users table was stored only in memory though, as it means all data is lost on a power down or reset. Tables could be recovered from backups, but as the police have those anyway it kind of defeats the purpose of having it in memory only.”

1. I live in America, so I’m not TOO worried about the Dutch Police coming after me.

2. Even though my account donated, it was a friend of mine that donated on my behalf so that I could give him an invite (yeah, it broke the rules….sue me). So they’d go after him before me =p.

3. I’m one of 180k+ users, not to mention I only DL’d like 6 gigs of old content. I would be low on their priority list.

All I have to worry about now is uploading my old Oink stuff to BOink.

lol?