> -----Original Message----- > From: shrike-list-admin@xxxxxxxxxx > [mailto:shrike-list-admin@xxxxxxxxxx] On Behalf Of Ow Mun Heng > Sent: Tuesday, October 07, 2003 10:05 PM > To: shrike-list@xxxxxxxxxx > Subject: RE: Which Firewall solutions > > > >>As for Tripwire, I have that on my list of things to learn. > At least > >>now know what it is. > > Tripwire's pretty easy to learn.. it's just setting it up. > You need to know what's installed in your system and _where_ > else you get config errors.. and stuffs like that.. > > PS : I've been reminded a couple of times already not to top-post.. > top post = posting on top of another's post without any > reference to what you're answering to.. > > no offense None taken. I am having a hard time conforming. 500 messages received today. 490 are about where to post an answer. 10 are questions that didn't get answered. Lol Jk Buck > > Cheers, .^. > Mun Heng, Ow /V\ > H/M Engineering /( )\ > Western Digital M'sia ^^-^^ > DID : 03-7870 5168 The Linux Advocate > > > > > -----Original Message----- > From: Buck [mailto:RHList@xxxxxxxxxxxx] > Sent: Wednesday, October 08, 2003 10:00 AM > To: shrike-list@xxxxxxxxxx > Subject: RE: Which Firewall solutions > > > No apology necessary, but I am embarrassed to say that when I > discovered the 2000 firewall and wanted to block all internet > access, I blocked ALL access. At least it was only setting > the computer up. > > As for Tripwire, I have that on my list of things to learn. > At least now I know what it is. > > lol, > Buck > > > > -----Original Message----- > > From: shrike-list-admin@xxxxxxxxxx > > [mailto:shrike-list-admin@xxxxxxxxxx] On Behalf Of Rodolfo J. Paiz > > Sent: Tuesday, October 07, 2003 8:51 PM > > To: shrike-list@xxxxxxxxxx > > Subject: RE: Which Firewall solutions > > > > > > At 15:04 10/7/2003, you wrote: > > >IF the network computers are running Windows NT Platform > > (NT, 2000, XP, > > >or future releases) or Linux boxes, then the internal > > firewalls on each > > >computer can be activated and provide an additional firewall > > on the LAN > > >computers. Same is true for the Internet boxes. Close all > > ports but > > >80 or whatever is appropriate. > > > > IMHO a machine's internal firewall code should always be > activated... > > always. I apologize for not noting that more clearly, Buck; > > you are correct > > in that it can be done, and I believe that it is a useful > > additional layer > > of security. Whenever possible, one should also arrange to be > > notified (by > > something like tripwire) if the firewall rules are changed at > > any time. > > > > > > -- > > Rodolfo J. Paiz > > rpaiz@xxxxxxxxxxxxxx > > > > > > -- > > Shrike-list mailing list > > Shrike-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/shrike> -list > > > > > > > > > > -- > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike> -list > > > -- > > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike-list > > > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
