Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 483160

Summary:	update to 5.3 installs and enables avahi
Product:	Red Hat Enterprise Linux 5	Reporter:	Ed Brown <ebrown>
Component:	avahi	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	high	Docs Contact:
Priority:	high
Version:	5.3	CC:	bgollahe, cww, jan.iven, kabbott, pasteur, reloftin, sta040, syeghiay, tao
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	599435 (view as bug list)		Environment:
Last Closed:	2011-08-12 15:03:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	502912, 599435

Description Ed Brown 2009-01-29 21:48:50 UTC

Description of problem:
Updating from RHEL-5.2 to 5.3 installed and enabled avahi (because of cups update - cups depends on avahi-compat-libdns_sd which depends on avahi)

Version-Release number of selected component (if applicable):
0.6.16-1.el5

How reproducible:
always

Steps to Reproduce:
1."yum update" on RHEL-5.2 system that does not have avahi installed.
2. reboot
3.
  
Actual results:
avahi is installed and running after reboot to new kernel

Expected results:
avahi should not be required by the compat libary rpm, avahi-compat-libdns_sd, and should not be installed because of dependency chains on systems where it is not installed

Additional info:
Automatic installation of daemons that open network ports and initiate broadcast traffic is a security significant event, and is unacceptable on enterprise servers.  I don't believe there's any reason avahi-compat-libdns_sd should require avahi, or if there is, avahi should not be configured to run by default.

Comment 8 Lennart Poettering 2009-12-17 18:48:07 UTC

The reason why avahi-compat-libdns_sd requires avahi is because it links against the avahi libraries that are part of the avahi package.

The proper fix would be to split the avahi libraries off into a seperate package. That would be a non-trivial packaging change however, not sure if that is suitable for fastrack.

Splitting off the libraries is already being requested in bug 530087.

Comment 12 Tim Waugh 2010-06-02 13:47:18 UTC

*** Bug 513559 has been marked as a duplicate of this bug. ***

Comment 23 Brian Gollaher 2011-08-12 15:03:45 UTC

Closing this as we do not want to change component behaviour in 5.8.