i should mention that the word "responsibility" is very loaded. it is a word that lacks conceptulisiation. fuzzy thinking people that don't know how to understand language misuse that word, since there is no right way to use it.

it slips loaded packets into the packetfilter causing a chain reaction that "unhooks" the firewall causing an exception to the packet filter, allowing access without having to get permission.
my knowledge of the internal operation is very limited. I sure know how to use it though.

That's not "loaded" at all. Simply put: you're free to do whatever you want, but you must be accountable for your actions. If you choose to use your freedoms to harm others, then society moves to contain/restrain you. People not comfortable with being accountable for their own actions like to toss around the term "Anarchist" as an excuse. "Hey man, I believe in Anarchy, don't hold me to your rules". Anarchy is usually used as an easy excuse to do whatever you want and not worry about consequences.

As for your so-called "firewall cracker", that sounds like one of the exploits that was demonstrated several years ago for FW-1. I highly doubt it actually works on anything in deployment today (other than ancient versions of FW-1), if you even possess such a thing. And thanks for confirming my skiddie suspicion. You don't know how it works, but you "know how to use it".

it slips loaded packets into the packetfilter causing a chain reaction that "unhooks" the firewall causing an exception to the packet filter, allowing access without having to get permission.
You seriously mean something more recent than CVE-2005-0449?

Heh, the SecurityFocus advisories involving that CVE are enlightening. It looks like early 2.6 kernels had a lot of "issues". I will grant there are likely a fairly large number of affected systems still around with vulnerable kernels.

I am going to join the chorus that says do a complete reinstall. The compromise was serious enough that you can never be sure the system is secure going forward. If the system is mission critical for the company, then bring up a new system to replace it and swap your critical data to the new machine after it is up and configured. Then completely wipe and start over with the compromised computer.

When you bring the system up originally, start with all ports closed, then start opening them selectively until you have only what you need. Make sure iptables (or ipchains if you are sticking with the 2.4 kernel) is up, running, and properly configured.

When I deploy a new server, after I have it up and running to my satisfaction, I immediately make an image of the system partition, which I then store on a DVD. Thus, should I find myself facing your situation (or, should a hard drive fail, etc), I can have my working configuration up and running again just as quickly as I can roll the image back onto the system. If I make significant upgrades or changes to the system, I make a new image.

You should establish this procedure for any business system you deploy. Combined with keeping /home on a separate drive from the system, you wind up with a capability to quickly recover from just about anything.

i use my freedom for my own honest interest only. the subhumans have constrained me and my actions for working for the good of everyone and the only way to make progress was to rebel. all philosophers of all stripes all say it EXACTLY the same way, "not without the sanction of the victim".

the linux version still works just fine. the windows version needs updates a lot.

yes, I admit to being a script kiddie.

to the best of my knowledge, it's update monthly.

As moderator I chose to close this thread as I should have done earlier on. People who read this thread should take post #14 as the end of this thread and treat the rest, with the exception of #20, as off-topic. If operator10001 or chort care to continue our discourse let me know and I'll move those parts to the General forum.