Torrent Configuration - Page 2

Hambergler · 07-22-2007, 03:35 PM

Quote:

Originally Posted by Acreo Aeneas

Manually opening ports usually means that when you're not using it, the port is still open. In other words, you open up 4 ports for a download. You step away for several hours and the download finishes. The ports you opened are still open, wide open. Some cracker (hacker isn't the proper term) could do a port scan on your router then see your opened ports. He/She could then proceed to implanting a keylogger to gather various personal and financial information on you, plant various viruses to "disable" your system, or even turn your machine into a zombie (unwilling participant in infecting other computers or systems).

Quote:

Originally Posted by =Sarc=

There's not much risk. It's only your bittorrent client responding on the port you've opened. Unless there's a security hole with the client you're using, it should be minimal risk.

Two different opinions. hhhhmmm. Anyone else care to share their security knowledge?

Lorian · 07-22-2007, 05:53 PM

I don't claim to be an expert on the subject, but as far as I know open ports on their own are not a security risk. It only becomes a problem when software listening on a port has either a security hole, granting access to outside users to stuff they shouldn't be able to, or malicious software is listening on a port. That is to say, a cracker can't just walk in through an open port.

Firewalls generally take a 'deny all except [whatever]' approach, so anything that may be listening on a port won't receive incoming packets unless it is specifically allowed to.

The standard SSH port (22) is a common target because if a cracker can log in as the root user then he can do anything to the system they wish. Having port 22 closed means any externally incoming packets are dropped (or rejected), while still working fine on the local network.

Boot · 07-23-2007, 01:09 AM

Update... I changed clients to uTorrent and used www.portforward.com to set things up. I'm testing a POE torrent and maxing at 538 kbps down!

Thanks for all the help guys!

**Apophis** · 07-23-2007, 08:47 AM

Quote:

Originally Posted by Hambergler

Two different opinions. hhhhmmm. Anyone else care to share their security knowledge?

I'll respond a little later today. There are potential risks with opening ports like this, but nothing that we can't take a couple extra steps to secure.

**Apophis** · 07-23-2007, 08:49 AM

Quote:

Originally Posted by Lorian

The standard SSH port (22) is a common target because if a cracker can log in as the root user then he can do anything to the system they wish. Having port 22 closed means any externally incoming packets are dropped (or rejected), while still working fine on the local network.

Port 22 is quite safe. Anyone operating a UNIX box with open 22 to the world that doesn't have "PermitRootLogin no" configured deserves whatever they get.

But this whole TCP/22 SSH deal is pretty irrelevant to this thread.

Acreo Aeneas · 07-23-2007, 09:42 AM

I don't think Boot or most of any of us in this thread (prob with the exception of Apo) runs a UNIX machine.

*awaits Apophis's comments/advice on open ports and security*

msdz · 07-23-2007, 10:37 PM

Utorrent seems to be a little easier to configure and reading and understanding the info that portforward.com gives makes things go a little easier.

=Sarc= · 07-24-2007, 10:18 AM

I've used uTorrent with XP and it has a UPnP feature that my router supports. It automatically opens the required port whenever it runs.

While Acreo says keyloggers and such can operate over a port that's been opened, those programs still have to infiltrate your system. Keep up with regular scans (I do weekly scans with NOD32). It should be safe to forward a port for torrenting as long as you do regular scans for spyware and malicious programs. A software firewall can help protect you too. This will stop unwanted programs on your system from accessing the Internet. Even then, you can always turn your computer off when it's not in use. That's the best security there.

icky · 07-24-2007, 11:16 AM

Quote:

Originally Posted by Hambergler

Two different opinions. hhhhmmm. Anyone else care to share their security knowledge?

The second opinion is correct. Open ports are only as vulnerable as the software listening on them. If you open a port to host a game, someone can potentially exploit a hole in the game server software to get something on to your computer.

07-22-2007, 05:53 PM	#17 (permalink)
Lorian Join Date: Feb 2006 Location: United Kingdom Age: 18 Posts: 2,036	Re: Torrent Configuration I don't claim to be an expert on the subject, but as far as I know open ports on their own are not a security risk. It only becomes a problem when software listening on a port has either a security hole, granting access to outside users to stuff they shouldn't be able to, or malicious software is listening on a port. That is to say, a cracker can't just walk in through an open port. Firewalls generally take a 'deny all except [whatever]' approach, so anything that may be listening on a port won't receive incoming packets unless it is specifically allowed to. The standard SSH port (22) is a common target because if a cracker can log in as the root user then he can do anything to the system they wish. Having port 22 closed means any externally incoming packets are dropped (or rejected), while still working fine on the local network. __________________ \|TG-E17th\|Lorian Member since 18th February 2006 Supporting member since 4th August 2006 PGP public key Processor: Intel Core 2 Duo E6420 Memory: 2x 1GB Corsair XMS2 DDR2-800 RAM Video Card: XFX NVIDIA GeForce 6800 XT 256MB Monitor: 17" Dell CRT and 15" generic LCD Sound Card: Creative X-Fi Xtrememusic and Creative Sound Blaster Live! (no Linux X-Fi drivers yet)

07-23-2007, 01:09 AM	#18 (permalink)
Boot Join Date: Aug 2005 Location: Wisconsin, USA Age: 37 Posts: 1,414	Re: Torrent Configuration Update... I changed clients to uTorrent and used www.portforward.com to set things up. I'm testing a POE torrent and maxing at 538 kbps down! Thanks for all the help guys! __________________ Boot. In Soviet Russia, TV watches YOU. Last edited by Boot; 07-23-2007 at 01:25 AM. Reason: Feed keeps getting faster!

07-23-2007, 09:42 AM	#21 (permalink)
Acreo Aeneas Join Date: Nov 2006 Location: DePaul University (Chicago) Age: 22 Posts: 4,547	Re: Torrent Configuration I don't think Boot or most of any of us in this thread (prob with the exception of Apo) runs a UNIX machine. awaits Apophis's comments/advice on open ports and security __________________ Acreo_Aeneas Former 9th MID Member Current Obsessions: Netbooks and other low-cost, small, and portable PCs.

07-23-2007, 10:37 PM	#22 (permalink)
msdz Join Date: Nov 2006 Location: WV Age: 36 Posts: 927	Re: Torrent Configuration Utorrent seems to be a little easier to configure and reading and understanding the info that portforward.com gives makes things go a little easier. __________________

07-24-2007, 10:18 AM	#23 (permalink)
=Sarc= Join Date: May 2003 Location: Ottawa, Canada Posts: 4,600	Re: Torrent Configuration I've used uTorrent with XP and it has a UPnP feature that my router supports. It automatically opens the required port whenever it runs. While Acreo says keyloggers and such can operate over a port that's been opened, those programs still have to infiltrate your system. Keep up with regular scans (I do weekly scans with NOD32). It should be safe to forward a port for torrenting as long as you do regular scans for spyware and malicious programs. A software firewall can help protect you too. This will stop unwanted programs on your system from accessing the Internet. Even then, you can always turn your computer off when it's not in use. That's the best security there. __________________ JO Guides & Tutorials Team Element - It's who you game with.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Sponsored links

Sponsored links

Sponsored links