[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] MYSQL Variables
- Subject: RE: [cobalt-users] MYSQL Variables
- From: "Clark E. Morgan" <prlhkr@xxxxxxxxxxxxx>
- Date: Fri Apr 6 05:34:04 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I am trying to disable one of the default variables
> MYSQL_TCP_PORT
If you comment out this line, MySQL will just start up with the
default of 3306 because it has to. See below...
> I simply want to disable mysql from running a socket connection
> on port 3306
> or any other port !
Uh, how are you going to connect to it if you disable the port? Unless
you plan on grabbing it by its rear quarters and mounting it from behind,
you are going to need a port. You don't have to accept the default; but
it's a database SERVER application and by definition it binds to a port
and accepts connections from CLIENTS, including PHP, and yes, even from
localhost. It won't run at all if it can't find a port to bind to. MySQL
gets very high marks consistently for their security and running MySQL as
an unpriveleged user; and further availing yourself of MySQL's sensible
grant table scheme, you can allow this without an unreasonable risk of
compromise.
As has been mentioned on this list several times, tongue in cheek but
nonetheless true, your security nightmare started when you hooked it to the
net. Right out of the box, your Raq has more security vulnerabilities than
MySQL simply doing its thing could ever cause you.
Relax and have fun. MySQL + PHP are a blast together.
Clark E. Morgan