Re: Many ports open by default

2001-05-07 Thread Turbo Fredriksson
Steve == Steve Greenland [EMAIL PROTECTED] writes: *beep, wrong* :) update-rc.d -f exim remove Steve *beep*, *wrong* :) Steve The problem with update-rc.d -f exim remove is that it Steve removes *all* the links, not just the S*exim links. Yes. That's a bug in

Re: Many ports open by default

2001-05-05 Thread Andreas Metzler
Tom Lear [EMAIL PROTECTED] wrote: Sure, don't run the daemon at all. When you install exim, rm /etc/init.d/rc?.d/S*exim and it won't start. Local processes will be BTW, I think this is what ssh should do if you choose not to run the daemon on startup (rather than making /etc/init.d/ssh not

Re: Many ports open by default

2001-05-05 Thread Torsten Landschoff
On Fri, May 04, 2001 at 07:12:07PM -0700, Tom Lear wrote: BTW, I think this is what ssh should do if you choose not to run the daemon on startup (rather than making /etc/init.d/ssh not work at all). I have ssh installed on my laptop, and I don't want it running by default, but I'd like to be

Re: Many ports open by default

2001-05-04 Thread Turbo Fredriksson
Quoting [EMAIL PROTECTED]: On Mon, Apr 30, 2001 at 11:52:46PM +, Will Lowe wrote: I think it's safe to assume that your system MUST have a working MTA of some sort (even if it's local-only, which is supported by eximconfig). This is true, but does it need to be world-accessible?

Re: Many ports open by default

2001-05-04 Thread Steve Greenland
On 04-May-01, 07:49 (CDT), Turbo Fredriksson [EMAIL PROTECTED] wrote: Quoting [EMAIL PROTECTED]: On Mon, Apr 30, 2001 at 11:52:46PM +, Will Lowe wrote: I think it's safe to assume that your system MUST have a working MTA of some sort (even if it's local-only, which is

Re: Many ports open by default

2001-05-04 Thread Matt Zimmerman
On Fri, May 04, 2001 at 02:49:47PM +0200, Turbo Fredriksson wrote: Quoting [EMAIL PROTECTED]: On Mon, Apr 30, 2001 at 11:52:46PM +, Will Lowe wrote: I think it's safe to assume that your system MUST have a working MTA of some sort (even if it's local-only, which is supported by

Re: Many ports open by default

2001-05-04 Thread Tom Lear
On Mon, Apr 30, 2001 at 11:52:46PM +, Will Lowe wrote: Sure, don't run the daemon at all. When you install exim, rm /etc/init.d/rc?.d/S*exim and it won't start. Local processes will be BTW, I think this is what ssh should do if you choose not to run the daemon on startup (rather than

Re: Many ports open by default

2001-05-01 Thread David Nusinow
On 30 Apr 2001 15:30:48 -0400, Wolfgang Sourdeau wrote: As always, that would be true if they weren't installed by default. The current method requires too much prior knowledge. This could be put as a question whenever someone installs Debian GNU/Linux. Something like Do you want to enable

Many ports open by default

2001-04-30 Thread Dwayne C. Litzenberger
I suspect it's already been discussed before, so I'll ask instead of flaming. (See! I can learn!) Why does a server automatically get run just because it's installed? For instance, portmap is installed by default whether you're using NFS or not, and bnetd runs even if I just installed the

Re: Many ports open by default

2001-04-30 Thread Sami Haahtinen
On Sun, Apr 29, 2001 at 10:29:58PM -0600, Dwayne C. Litzenberger wrote: Why does a server automatically get run just because it's installed? For instance, portmap is installed by default whether you're using NFS or not, and bnetd runs even if I just installed the package for bnchat. Shouldn't

Re: Many ports open by default

2001-04-30 Thread Andres Salomon
Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to run. If i install exim, it will first configure it for me (prompting me), and then assume

Re: Many ports open by default

2001-04-30 Thread Aaron Lehmann
On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. That's not true. inetd is depended on by the lame metapackage netbase,

Re: Many ports open by default

2001-04-30 Thread Andres Salomon
On Sun, Apr 29, 2001 at 11:43:43PM -0700, Aaron Lehmann wrote: On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it.

Re: Many ports open by default

2001-04-30 Thread Warren A. Layton
On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to run. Well, not

Re: Many ports open by default

2001-04-30 Thread Paul Martin
On Mon, Apr 30, 2001 at 08:45:44AM +0300, Sami Haahtinen wrote: The 'exit 0' line in the beginning of the init file is a bad idea. for so many times i've commented out the '### comment this line to really start the service' lines. and then after upgrade gotten in to the position where i have

Re: Many ports open by default

2001-04-30 Thread Dwayne C. Litzenberger
Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to run. I may want to look at the package's documentation, or use some tool that's not

Re: Many ports open by default

2001-04-30 Thread Anthony Towns
On Mon, Apr 30, 2001 at 07:37:21AM -0500, Warren A. Layton wrote: On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it.

Re: Many ports open by default

2001-04-30 Thread Dwayne C. Litzenberger
I'm not suggesting we ruin anything. exit 0 isn't the only way to disable something by default. My main concern is of security. I know a newbie who installed Debian recently, and he has something like 15 open ports, which wouldn't be a problem except for the history of these daemons to have

Re: Many ports open by default

2001-04-30 Thread Josip Rodin
On Mon, Apr 30, 2001 at 07:37:21AM -0500, Warren A. Layton wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to run. Well, not

Re: Many ports open by default

2001-04-30 Thread Josip Rodin
On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: The question you should be asking is, why is portmap installed by default? Fortunately, nowadays it can be removed since it's no longer part of netbase. -- Digital Electronic Being Intended for Assassination and Nullification

Re: Many ports open by default

2001-04-30 Thread Craig Sanders
On Sun, Apr 29, 2001 at 10:29:58PM -0600, Dwayne C. Litzenberger wrote: I suspect it's already been discussed before, so I'll ask instead of flaming. (See! I can learn!) many times before. Why does a server automatically get run just because it's installed? because if you didn't want it to

Re: Many ports open by default

2001-04-30 Thread Craig Sanders
On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: If there's nothing that depends on portmap, then default to not installing portmap. speaking of portmap, debian's portmap is not an insecure thing to run by default because it is compiled with tcp-wrappers support and rejects all

Re: Many ports open by default

2001-04-30 Thread Craig Sanders
On Mon, Apr 30, 2001 at 07:37:21AM -0500, Warren A. Layton wrote: Well, not everyone that installs ssh wants to run the server (some may just want to use the client to connect to other machines). This is just one example; I'm sure that there are many more. that means either: 1. ssh and sshd

Re: Many ports open by default

2001-04-30 Thread Frederico Muñoz
Warren A. Layton wrote: On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to

Re: Many ports open by default

2001-04-30 Thread Michael Stone
On Tue, May 01, 2001 at 12:22:47AM +1000, Craig Sanders wrote: On Sun, Apr 29, 2001 at 10:29:58PM -0600, Dwayne C. Litzenberger wrote: Why does a server automatically get run just because it's installed? because if you didn't want it to run, you wouldn't have installed it. As always, that

Re: Many ports open by default

2001-04-30 Thread Warren A. Layton
On Tue, May 01, 2001 at 12:28:49AM +1000, Craig Sanders wrote: 1. ssh and sshd should be split into separate packages. if it bothers you enough, file a bug report. i'm happy with the way it is. or 2. the handful of people who want the ssh client but not the ssh daemon can learn how to

Re: Many ports open by default

2001-04-30 Thread Wolfgang Sourdeau
As always, that would be true if they weren't installed by default. The current method requires too much prior knowledge. This could be put as a question whenever someone installs Debian GNU/Linux. Something like Do you want to enable the installed server software by default. Beware that this

Re: Many ports open by default

2001-04-30 Thread mdanish
On Mon, Apr 30, 2001 at 02:25:34AM -0400, Andres Salomon wrote: Why would you keep something around if you don't want to run it? Debian makes the (correct) assumption that if you've installed something, you want to run it. If i install bind, it will assume i want it to run. If i install

Re: Many ports open by default

2001-04-30 Thread Will Lowe
Actually there are some packages that depend on a mail-transport-agent, (such as lilo-logrotate-mailx), yet one may not want to have an MTA running on certain systems. I suppose a dummy or minimal MTA may be I think it's safe to assume that your system MUST have a working MTA of some sort

Re: Many ports open by default

2001-04-30 Thread Matt Zimmerman
On Tue, May 01, 2001 at 12:22:47AM +1000, Craig Sanders wrote: On Sun, Apr 29, 2001 at 10:29:58PM -0600, Dwayne C. Litzenberger wrote: I suspect it's already been discussed before, so I'll ask instead of flaming. (See! I can learn!) many times before. Why does a server automatically

Re: Many ports open by default

2001-04-30 Thread mdanish
On Mon, Apr 30, 2001 at 08:12:59PM +, Will Lowe wrote: Actually there are some packages that depend on a mail-transport-agent, (such as lilo-logrotate-mailx), yet one may not want to have an MTA running on certain systems. I suppose a dummy or minimal MTA may be I think it's safe to

Re: Many ports open by default

2001-04-30 Thread Will Lowe
I think it's safe to assume that your system MUST have a working MTA of some sort (even if it's local-only, which is supported by eximconfig). This is true, but does it need to be world-accessible? There should be a way to either have it listen on localhost only, or not listen on Sure,

Re: Many ports open by default

2001-04-30 Thread mdanish
On Mon, Apr 30, 2001 at 11:52:46PM +, Will Lowe wrote: I think it's safe to assume that your system MUST have a working MTA of some sort (even if it's local-only, which is supported by eximconfig). This is true, but does it need to be world-accessible? There should be a way to