Just post whatever program you use to block unwanted traffic AP2P or what ever it is. And programs or sites relevant to its working.
Also if you have tried other programs list them and a reason you prefer your current program over that.
List factors that you like and dislike about the program. The aim is that if you were having an issue with a certain aspect of your program you could look on here and see something that was a viable alternative.
It took time to make it into what I needed it for.
Runs consistent.
Is easy to program if you know how to program as its open source.
Free to use and download.
Not sure what else to say. Well I guess I would not recommend it to someone who was just looking for a program to download click run and leave it be. Like I said its only as good as you make it.
It took time to make it into what I needed it for.
Runs consistent.
Is easy to program if you know how to program as its open source.
Free to use and download.
Not sure what else to say. Well I guess I would not recommend it to someone who was just looking for a program to download click run and leave it be. Like I said its only as good as you make it.
iptables, but I really use it only to protect myself from too many request in a short time to prevent ssh hacks.
Name:
Anonymous2010-10-01 18:35
For iptables.
What sort of CPU does it use when operating?
It has the ability to monitor a connections state and redirect it, change and stop data packets based on the state. Is this on just the source or destination packet data content to?
Name:
Anonymous2010-10-01 18:51
BSD's ipf > *
Name:
Anonymous2010-10-01 18:53
I'm not sure what you are saying about ssh hacks but.
I use iptables to block the whole Internet for my user that uses wine to run games from inferior OS on my Linux. That's why I'm not afraid to run *.exe from /b/ itself.
Name:
Anonymous2010-10-01 23:24
I'm not sure what you are saying about ssh hacks but.
>>21
I'm not sure if I was >>20 or not, but I remember reading this thread. as far as I know, a process in wine can still make a regular syscall (Linux, or whatever the host OS running wine is) if it knows it's running in wine, and it can try to exploit any vulnerability in wine (if one is known) to try to break out of the virtualized file system.