Re: cvs commit: src/etc inetd.conf
From: Alexander Langer (alex@big.endian.de)
Date: 08/15/01
- Next message: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Previous message: Krzysztof Zaraska: "Re: Question about default IPFW Rules..."
- Next in thread: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Reply: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Maybe reply: Brian Somers: "Re: cvs commit: src/etc inetd.conf"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 15 Aug 2001 13:48:52 +0200 From: Alexander Langer <alex@big.endian.de> To: Robert Watson <rwatson@FreeBSD.org>
Thus spake Robert Watson (rwatson@FreeBSD.org):
> processing out of cron, not bind sockets, etc. I don't know much about
> that, from an operational perspective, and would be interested in hearing
> more about the considerations here. For example, I do know that a number
> of system functions generate e-mail (scheduled events, vi recovery, etc)
> and that needs to be handled properly.
We can disable binding to port 25 and local mail delivery will still
work. I also like disabling all other network services by default.
One of OpenBSD's argument is, that you then know what services you've
had enabled, and you then know, what to take care about. If you
missed a SA about some service you haven't enabled either, who cares?
Alex
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Previous message: Krzysztof Zaraska: "Re: Question about default IPFW Rules..."
- Next in thread: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Reply: Sheldon Hearn: "Re: cvs commit: src/etc inetd.conf"
- Maybe reply: Brian Somers: "Re: cvs commit: src/etc inetd.conf"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|