Quote:
Originally Posted by RycEric
Uploaders can be identified, using the legal system, and is exactly part of our strategy this year. It's working quite nicely. Ask the guy who uploaded 37K pics/vids to a popular tube site and found his account canned after the tube site received a court order for his info.
|
The thing is that, if its really user uploaded, the tube still gets profited and gets not punishment for this while his surfers audience keeps rising, and if its the owner who uploads it and its skilled enough, believe me, there is no way you could track him down .... It just came to my mind two ways of doing so without leaving a TCP track of all this ....
btw, something funny i always wondered, i see all the time this stuff about the tube/site/etc giving out server logs in order to track down someone, are you aware how easy that is to forge? I could do it by simple running a script and modify ips or even making it as complex as developing a daemon plugin or kernel module to forge them each time the web server wants to write the real IP so even if you where infront of the pc waiting for the log line to appear, it would not be the real IP ....
I would never rely on a server log ( On server side ), i would rely on the hostings companies switch logs MAYBE, but i'm not sure they really have one, and still if it did, i'm not sure you can match them technically speaking to the HTTP TCP connection that the HTTP WEB SERVER daemon thread/process that actually took care of uploading that content ... So then you would only have probes there was a lot of bandwidth going upstream from X IP ( which off course can be forged in many other ways, we wont enter on that one ), but you then had off course to track the IP which can be pretty difficult or even impossible if uploader is skilled enough, and on the other hand, it still doesn't probe the uploader uploaded THE CONTENT BEING INFRINGED, the switch would at most keep track of dates and ammount of bandwidth and maybe matching source/destination ports to the server, but server does not save on the logs the port from where connections come, and they are not fingerprinting the data that passes through them, actually i think that would be illegal .... that actually would be like the famous government sniffing emails/etc stuff which people wont never accept.
So you are on a dead end there too if you are facing a skilled enough uploader ( Which could be a non skilled at all honestly if he just connected himself and uploaded it from a wifi connection on a bar that has no cameras and you can't track him down [ The other options i was thinking are pretty more advanced and would let him use high bandwidth servers ;) ] ).