Bit-torrent clients are quickly becoming the preferred peer-to-peer filesharing applications mainly due to their high speed download abilities. They are capable of downloading at much higher speeds than network based peer-to-peer software such as limewire or frostwire which rely on the gnutella network. The mistake that most first-time bit torrent client users experience is that they do not configure the software properly which, according to software developers, limits both the upload and download speed of your software. However, there are security risks brought on by configuring these programs the intended way and by configuring my applications more for security, I have not experienced slower download or upload speeds in any way. It is true though, that users will not be able to connect to me in order to download via the DHT (trackerless) network, however I can still seed and upload files normally.

The correct way to configure a bit-torrent client, such as bitcomet, is to configure your modem/router to forward (open) a listening port to receive inbound connections from other users client software and configuring your firewall to accept inbound connections through this port. The problem with opening up a port is that you will willfully be accepting incoming connections from various ip addresses from all over the world. Unless you use an ip blocklist you are then guaranteed to have bad ip ranges connecting directly to your computer. However, ip blocklists only tend to block out around 80% of bad ip ranges at maximum. Despite a lot of speculation on this issue, you are only as secure as the program listening on that port. If your bit-torrent software is accepting inbound connections then it needs to be monitoring every single ip address's activity to ensure that there is nothing untoward occurring, then banning any ip address that may have risks associated with it. However, there are no bit-torrent clients that state that this procedure is performed and even if they did, there is still a huge risk. There are now a lot of fake files and virus torrents being hosted on torrent websites, mainly put in place by governments in attempt to deter filesharers. Many of these government agencies will use a reconfigfured bit-torrent client to try to make a direct connection to your computer should they find you downloading one of their files and who's to say what sort of thing they are capable once they have established that direct connection. Governments have access to a lot more advanced software than home users and they may be even keep track of all the ip addresses that the hosted file has received hits from. Should you be attempting to download copyrighted material, they may then send out a government warning to your internet service provider for you, warning you to stop or be cut off. They could also infect the files with specially crafted software that, once downloaded, allows them access to your computer. Governments may have the legal right to develop this kind of software but, of course, once detected will most likely be discovered and recognized as viruses by various scanning tools and may even be discovered immediately using heuristic scanning.

Software such as bitcomet suggests at startup, if you are using xp service pack 2, that you should patch your tcp/ip limit and allow between 50 - 200 half-open (unestablished) connections. In sp2 there is a default security limit of 10 half-open connections per second. This limit is put in place to stop malicious viruses and worms spreading infections over the internet in large volumes. Of course, if you have an open port and someone connected to you is making a large volume of unestablished connections to your ip address then how are you going to determine whether this is a genuine connection or a worm trying to find its way into the open port? You can't. Patching the tcp/ip limit is an old technique and was originally intended for use on dial-up connections. On faster broadband connections the technique/patch is pretty much redundant as it will probably only help to make your initial connection to your peers a little faster at startup. Half-open/unestablished connections are only going to be dropped in the end anyway and it will probably therefore be more likely to slow things down. If a machine is infected and has been turned into a spambot, then it will be attempting to make large volumes of half-open connections in order to spread infection quicker. Remember, it's better to be safe than sorry!