[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RE: Close some ports
- Subject: Re: [cobalt-users] RE: Close some ports
- From: shimi <shimi@xxxxxxxxxxxxxxxx>
- Date: Sun Mar 11 10:10:35 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Now I meant that you should configure the firewall to allow packets to
the port of imap to come only from SRC 127.0.0.1, by that you'll allow
local connections like the active monitor but block connections from the
outside world.
Best regards,
shimi [mailto:shimi@xxxxxxxxxxxxxxxx]
----
There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence.
-- Jeremy S. Anderson
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
BSD: "Are you guys coming or what?"
On Sun, 11 Mar 2001, Craig Napier wrote:
> >Did you guys think of firewalling the port with ipchains from connections
> >coming from eth0?
> >or have him only bind to 127.0.0.1 via his config?
>
> Actually my firewall does have it on 0.0.0.0 (as listening) but I have to
> ask, how do you bind IMAP on 127.0.0.1 via the config? I opened up the
> config and changed his path to "internal", which a qucik check of netstat
> shows it did close the port -but amber flashy came back in the GUI as
> well...
>
> Changed from:
> imap stream tcp nowait root /usr/sbin/tcpd imapd
>
> To:
> imap stream tcp nowait root internal imapd
>
> I'd just like to disable the damn thing... I don't mind the monitor-part,
> but I don't want IMAP running at all from my inetd.conf file..
>
> Thanks!
> Craig
> Thanks
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>