-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, think of it like an office building. When everyone goes home
at night and your security force is patrolling the building, would
you rather them allow entry to the building to anyone who wants
except for those you list to stop entry ("That was Charles Manson?
Hmmm, he wasn't on the list, so I didn't recognize him.), or only
allow people who can prove they should be there? Same thing applies
to guarding your system or network. You can never know all possible
attacks, so the safer way to run things is to not let anything in
except what you know you need and/or are willing to take the risk of
harm from.
Randy Graham
- -----Original Message-----
From: Sebastian Sohn [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, February 28, 2001 9:39 PM
To: [EMAIL PROTECTED]
Subject: firewalling rules
I am new in firewall configuration. It seems that when I read
articles on
the web, people suggest that, one should setup the firewalling rules
to deny
everything and allow specifics?
What is wrong with having a rules accept all but deny specifics.
Could I not just block ports that I am using, like telnet 23 , ftp 21
, ssh
22, NetBIOS 135-139 and such. Why should I block everything coming
in?
Thanks!
- -Sebastian
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
- -
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.3
iQA/AwUBOp6Yk/ZOhQpA1TB+EQIq6ACgltghvWBz1epTjkHZsrfvw9m9qRsAoJMt
0y/9m/UUkaGQHAEWki4Gd6+0
=XvCj
-----END PGP SIGNATURE-----
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
