Btw, I'm satisfied now with my current network policy and how I implemented
that policy through ipchains. I also patched and cured linux's incorrect
perms, vulnerabilities, etc.
It's also good that I've included logging in my ipchains. I just found that
someone was trying to remotely mount my NFS. Too bad for that guy, I don't
have NFS enabled.
Yes, /etc/hosts.allow and /etc/hosts.deny can really help. This is being
used by TCPWRAPPERS, I guess. ;-)
You also have to consider your internal network. Most attacks come from the
inside. So don't trust anyone. Bury your linux 10 feet deep down the floor.
Kidding ;-)
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 31, 2000 9:30 AM
> To: '[EMAIL PROTECTED]'
> Subject: Re: [plug] OT: Firewall Policy Rules
>
>
> You mean /etc/host.deny and host.allow must be configured?
>
> -------------------------------------
> Roi
> Angeles Communications (Phils.), Inc.
> -----------------
> Proverbs 8:13
>
>
> On Thu, 23 Mar 2000, Michael Vincent K. Pozon - CompE wrote:
>
> >
> > Depending on your network topology:
> > If you're linux box is acting as a router , you may use
> ipchains , but if
> > you use your cisco router for all network connectivity, then use
> > access-list.
> >
> > You may want to describe you network topology/setup if you need more
> > syggestion ;)
> >
> > On Thu, 23 Mar 2000, Ronneil Camara wrote:
> >
> > > Which is better, ipchains or cisco's extended
> access-list? Should I be
> > > comfortable with ipchains instead of having a real
> firewall software like
> > > TIS or Checkpoint?
> > >
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
