Quote:
|
Originally Posted by w5set
Well--now if he has used a default install of the repo available Bittorrent, then it uses 6881-6889 for default ports.
So why would he have the upper ports being used?
I am VERY aware that bittorrent can be setup to use just about any port that is normally open to the net--but I doubt he has enabled the upper ports for this use.
Most of the "shared" torrent (screen shot) is USING the normal 688X ports--so why would he have users on the higher ports???
Unless firestarter is showing the ports USED on the other end?
|
I'm going to try not to flame, but what would you expect after posting such a rant? There are several things you obviously don't understand about TCP/IP, let alone BitTorrent. Therefore, I will try to explain.
The default ports for BitTorrent (6881-6889) are a range of ports from which one is chosen when BT first starts. This port is for
listening (aka a server port) and is a control port like FTP's port 21. No downloading or uploading occurs on this port. Additional ports for sharing files are chosen dynamically as they are needed from the range of all available ports (except privelaged ports 1-1024, if I remember correctly). Firestarter (as shown in the screen shot) was only showing the port on the remote side of the connection. It was also showing that the connection (with the service labled "Back Orifice 2k") was initiated from the local computer to the remote computer.
Quote:
|
Originally Posted by w5set
Bittorrent is one app that isn't absolutely secure and safe, there's been numerous users who will hog the bandwidth (leeches) and not share with other children very well. There are several versions of "torrent" software out on the internet with "extra features" installed....(don't just grab torrent software from just anywhere) ....so lets don't just assume everything is just fine and dandy, yet...
|
Your use of the name BitTorrent becomes ambiguous here. Are you talking about the app or the protocol? Yeah, there could be problems in the protocol. I also don't trust just any client app either. Now you certainly don't understand what a leacher is. They have nothing to do with security, they just don't wan't to share bandwidth and it is a valid option in the protocol. They are freeloaders, not bad guys. And the protocol is actually designed to penalize freeloaders with slower download times.
Quote:
|
Originally Posted by w5set
Anyone who believes Linux is safe from exploits has had their head buried in the sand too long---come up for air....
It's not just all peaches and cream out in Internet Land just yet.
/off rant
|
I certainly don't think Linux is invincible (unless you configure it right

), but anyone who uses a well designed and properly configured distro can go out into the virtual world confidently wearing the armour of Linux. It certainly doesn't mean you can run around the net ignorantly, so keep your guard up, but don't fret about every stupid little thing. Also, users should go learn something now and then. It is often users or admins doing something stupid that compromize a Linux box. The whole issue surrounding this thread is that code_astronomer didn't know all the details about how BT uses ports and Firestarter was unclear about what was really going on (something that will have to be improved in Firestarter). I clarified most of the details and then you start crying wolf. I don't appreciate it and it certainly doesn't help code_astronomer any.
ps - If I made any errors in any technical details or mistyped somethiing, deal with it! I've wasted enough time responding already. I'm getting dizzy picking apart this rant and have better things to do. I feel I've sufficiently made my point.