ISPs Monitoring sharing

[hyst3rical]

My ISP apparently monitors my file transfers. I had my access turned off :shootand they sent me a letter complaining that I was sharing (uploading) movies. :cross At the time I was using Shareaza on my PC, now Im using Azureus on my G5. My question is can my ISP tell the files I'm sharing thru a torrent jus like they can Kazaa? or is BitTorrent set up differently? I enjoy optimizing my cable connection to retrieve my backed-up DVDs that I have purchased, but I don't want my ISP turning my internet service off and threatening to alert federal authorities. :devil Any input on this would be fantastic! Happy Sharing!


J.

[dock0184]

Threaten them that you'll switch ISPs. But you may have to. One way to possibly avoid it is to route the filesharing app thru port 80 (http port). Second way is to use an encrypted p2p app (like waste). (Does anyone know if you could also tunnel a normal p2p app thru SSL?)

The federal govt doesn't care what you share, as long as you're not a pirate (someone who duplicates copyrighted stuff to make $$$).

Broadband without p2p, is like a wedding without a groom.

[hawkburn]

The federal govt doesn't care what you share, as long as you're not a pirate (someone who duplicates copyrighted stuff to make $$$).
Actually they do. They're influenced by the major corporations (RIAA, MPAA) and thus in a few months will give the DOJ the authority to prosecute people just like the RIAA.

[dock0184]

Actually they do. They're influenced by the major corporations (RIAA, MPAA) and thus in a few months will give the DOJ the authority to prosecute people just like the RIAA.

Yea, I was talking in the context of Feds actually coming after you, which hasn't happened yet for the small p2p user. I can't see the DOJ running around suing everyone for sharing files, though Ashcroft is a bastard! :finger

[FrozenShadow23]

Use non standard ports. If the program you are using doesn't support changing the ports, do it yourself with SocksCAP. If you can't find a copy, PM me or Email me. BTW, I think it does support SSL.

[hyst3rical]

I have been doing some research on my ISPs terms and the only thing that they DO allow is downloading MUSIC, and NOT uploading it. They stick real close to the DMCA. So, in order to do my share, I need to know if they only monitor certain ports for sharing, or if they monitor ALL files transferred to check for copyright infringement. If it is just certain known file-sharing ports, that will enable me to just change the ports im using. If they check ALL files, I think I will need some sort of way to secure my transfers so they cant see exactly what the file is. If anyone has any answers I would be greatly appreciated. Thanks.

[eivioolla]

Anything with real encryption should stop them from monitoring your traffic. In theory encryption could be cracked but I don't think they go that far any time soon.

[shawners]

they arent monitoring you at all, mpaa found the infringing files and sent your isp the warning.. They must respond by first warning, then terminating service if you still dont comply. Dont delete the movies, they cant tell if you have them on just cause your on the internet. There being shared, and in which mpaa/riaa bots do search and record your isp number. So thats how the ISP knows whats going on. I dont think they have the manpower or time to monitor each infringer or person on their network.. Or resources.

[SamJam]

You really need to be careful using BT clients (Azureus). You're uploading the file the same time you are downloading it. Like shawners said... the MPAA has downloaded and warned your ISP. It may not be wise to use a BT client if you have already been warned once.

BTW... Who is your ISP?

[TNAVi]

I'm with shawners on this: An ISP staff would have to have the eyes of a fly (and a hell of a lot of time on their hands) to monitor the hundreds of thousand IP's and the files that are being transferred. I have been using BT ever since it was released and it has always been good to me. And like the forum member mentioned you were notified only because RIAA/MPAA bots tracked you and not the ISP.

Your security measures were nonstandard for that to happen. If you BT you should use PeerGuardian which has RIAA/MPAA and many bot sniffing organizations IP's blocklisted (another term "blacklisted" or "simply "blocked" from accessing your computer.) On top of that you can also add the blocklisted IP's to your Firewall. So many say that when you use BT your IP is exposed, while true, your IP is exposed regardless as long as you are on the Internet. Clients like Kazaa are pure setups because you have to setup shared folders exposing all the gigs of stuff you have to share, that can easliy be captured via a screenshot of your shared folders. However with BT you are not entitled to setup a shared folder and the only files one can assume you are sharing are the one being downloaded at the current moment. So in essence BT is safer than shared folder P2P clients.

An ISP that blocks ports and only allows common HTTP and FTP ports is not worth joining. I use the same port 6881 for my FTPServer just in case I'm ever questioned. Another point is that just because your IP is exposed on BT networks does not mean that you have 100% of the file; and if you don't have 100% you literally don't have it and should not be questioned by the RIAA/MPAA or your ISP. One would have to prove that you actually have the files first and thats kind of hard to prove using BT unless you have low security standards on your computer. Like I said you can monitor me downloading/uploading a file all you want BUT there's is no proof that I have the file or have uploaded 100% of the file. There is always an argument on your behalf that their were crc errors and your download/upload is corrupt. It can't be proved unless they take your computer and search your HD.

What you have to watch out for is sneaky little .dll files that communicate with COM objects that report information back to RIAA/MPAA bots that "phone home" and tell them whether or not you deleted the file, moved them to another HD, or burned them to CD or DVD media (as all of your activites and/or program activities are logged and sent.) A good reverse engineer can always decompile an executable, add a little something and recompile it so there is an extra file resting in your system32 folder...nonetheless just don't use shared folder P2P clients and use BT. And just argue with your ISP that your files are corrupt and don't work anyway--so why bother you with something you don't really have.

[hyst3rical]

Adelphia is my ISP. I'm using PG now. OS X 10.3.4. Seems like I should be fine now... (?) I hope. :)

[gajans]

Hyst3rical,

I was just wondering if they specifically said that you were sharing movies, or if you uploaded too much cuz i haven't heard of any isps caring about filesharing as long as you don't strain there system and some have caps on how much you can upload and download in a certain month in the terms of services. My isp has a rediculously low cap but i've never heard of them enforcing it. They do say that they will cut of your internet fo 3 days if they catch you the first time.