Bug 109424 – MySQLd bounded to all IPs (per default without root password)

Bug 109424 - MySQLd bounded to all IPs (per default without root password)

Summary:	MySQLd bounded to all IPs (per default without root password)

Status:	CLOSED DUPLICATE of bug 88352

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	mysql (Show other bugs)
Sub Component:
Version:	1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Patrick Macdonald
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-11-07 13:30 EST by Robert Scheck
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:59:49 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Robert Scheck 2003-11-07 13:30:49 EST

Description of problem, how reproducible and steps to reproduce:
If I install the latest mysqld package (Fedora Core 1 or Red Hat 9), per default the mysql daemon is bounded to all available IPs.
I wouldn't see that as real bug or critical security problem, but I personally think it's comparable as a Fedora installation without a password ;-)
So let me say: If you install a fresh system, you normally don't configure a mysql server at first, also there is a unrequested mysql root access by network possible...

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

Actual results:
Maybe it's a possibility to bind mysqld to 127.0.0.1 at installation. If the user needs external mysql access he can change that.

Comment 1 Patrick Macdonald 2003-11-10 10:14:35 EST

This is a duplicate of the mentioned enhancement.  At the moment,
the default behaviour from MySQL is being used.

*** This bug has been marked as a duplicate of 88352 ***

Comment 2 Red Hat Bugzilla 2006-02-21 13:59:49 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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