Bug 146368 - mDNSresponder should not be enabled by default
mDNSresponder should not be enabled by default
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: howl (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Depends On:
  Show dependency treegraph
Reported: 2005-01-27 11:35 EST by Zenon Panoussis
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-27 11:55:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zenon Panoussis 2005-01-27 11:35:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:

A fairly conservative approach in enabling network services by default
is a Good Thing[tm] and it is also RH policy. Rendevous is not
indispensable or even necessary for networking. In fact, in the
typical RHEL server installation it is plainly redundant. Thus, I
think it should be left up to the individual admin to enable it.
Currently it gets installed and enabled by default. 

This applies to FC too. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install RHEL
2. Boot

Actual Results:  mDNSresponder is running
Expected Results:  mDNSresponder should not be running
Comment 1 Alexander Larsson 2005-01-27 11:55:41 EST
Its needed for a good "desktop experience", and desktop users won't be
configuring it manually, so its enabled to get a good out-of-the-box
experience (if howl + desktop is installed). However, server admins
are able to disable it if they want.
Comment 2 Zenon Panoussis 2005-01-27 12:17:08 EST
If a "good feeling" is the only purpose, then perhaps it could stay
enabled in FC and WS, but not in AS/ES.  One day in the dark future,
200.000 users will be bitten by an exploit in a service they didn't
install and I'll say "what was it I said". Oh well...

Note You need to log in before you can comment on or make changes to this bug.