This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 88134 - RFE: place #skip-networking in /etc/my.cnf for mysql to avoid security issue
RFE: place #skip-networking in /etc/my.cnf for mysql to avoid security issue
Status: CLOSED DUPLICATE of bug 88133
Product: Red Hat Linux
Classification: Retired
Component: mysql (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-06 10:49 EDT by Bryce Nesbitt
Modified: 2007-04-18 12:52 EDT (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description Bryce Nesbitt 2003-04-06 10:49:34 EDT
Description of problem:
-----------------------
Many people run mysql on the same machine as the web server, and thus don't need
external networking enabled at ALL.  A service that is turned off is always more
secure than a service that's turned on.

Mysql comes by default with:
   * no root pasword
   * external network enabled
   * a variety of default accounts


Proposed solution (for /etc/my.cnf):
------------------------------------
If you'd add a commented-out "skip networking" line in /etc/my.cnf, more people
would discover how to turn off networking:  

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
#skip-networking

[mysql.server]
user=mysql
basedir=/var/lib
#skip-networking

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
#skip-networking
Comment 1 Patrick Macdonald 2003-04-07 09:02:08 EDT
Bug opened twice. Marking it as dup of 88133.

*** This bug has been marked as a duplicate of 88133 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:52:30 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.