Bug 88352 - rfe: mysqld should bind only to localhost by default instead of 0.0.0.0
Summary: rfe: mysqld should bind only to localhost by default instead of 0.0.0.0
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mysql
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom Lane
QA Contact: David Lawrence
URL:
Whiteboard:
: 109424 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-09 10:57 UTC by Toni Willberg
Modified: 2013-07-03 02:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-03 19:10:34 UTC

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

Description Toni Willberg 2003-04-09 10:57:18 UTC 
Hello.

By default mysql-server installation configures mysqld to listen on all
addresses (0.0.0.0).

I suggest changing the default configuration to bind mysqld only to localhost
(127.0.0.1) by adding "bind-address=127.0.0.1" to /etc/my.cnf.

There should be no need to listen on 0.0.0.0 right after installation, as the
database is empty anyway.


Version-Release number of selected component (if applicable):
mysql-server-3.23.54a-4
Comment 1 Nathan G. Grennan 2003-05-05 16:35:09 UTC 
I agree with you. I have been adding --bind-address=127.0.0.1 to
/etc/rc.d/init.d/mysqld on the safe_mysqld line. I don't trust the acl not to
allow someone to buffer overflow or exploit mysqld in some way. Even if it is
just DDoS.
Comment 2 Toni Willberg 2003-05-28 12:30:59 UTC 
Still valid for mysql-server-3.23.56-2.
Comment 3 Patrick Macdonald 2003-11-10 15:14:37 UTC 
*** Bug 109424 has been marked as a duplicate of this bug. ***
Comment 4 Tom Lane 2004-02-03 19:10:34 UTC 
I'm a bit hesitant to override the upstream's opinions about how to
configure their software.  If we do this then Red Hat installations
will behave differently from everyone else's, and we'll get bug
reports about how people can't connect to their MySQL servers.

I'd suggest taking it up with MySQL AB and seeing if you can convince
them it's a good idea.
Note You need to log in before you can comment on or make changes to this bug.