> 1) What about a warning note on some random ports like the "this x is
> for company x use only. No one else has permission to access this
> device. blah, blah, blah. Disconnect now!" which would give a better
> legal position should someone need to be prosecuted for doing
> something they shouldn't have. Simply initiating a connection to the
> selected port would pump the message out to them
> (a la -> "NC -l -p x < warningfile.TXT")
> This may alreay be the norm, I don't know.
> 2) What about tying up/closing ports during certain hours. Leave ports
> x,y, and z open during buss hours but close the ones you don't need
> (say y, and z) during off hours. I don't know if most firewall
> solutions out there allow you to do this or not. even if they didn't
> a simple script could tie up the port and feed it some periodic data
> (to keep from timing out) until it was time to open them again.
> If the current solutions do NOT allow timed rules, they SHOULD.
These are interesting ideas but they are bandaids for the real problem.
The issue is one of ecomonics and law. What needs to happen is for
bills to be proposed to your state legislature or the U.S. Congress,
have them vigorously debated using a gaggle of experts pro and con, and
then either pass into law or reject the bill. If the law is passed then
it can be tested in the courts to see if it flies. That's the way it
works in our constitutional democratic republic.
Paul
---------------------------------------------------------------------------
Paul B. Brown [EMAIL PROTECTED]
President
Brown Technologies Network, Inc. http://www.btechnet.com/
Systems and Applications Design, Development, Deployment, and Maintenance
---------------------------------------------------------------------------
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
