You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2019. It is now read-only.
I.e. loopback logins are possible without the root password. Logins from outside loopback are not permitted btw. So the root password we set up is pointless. (As well as the root user being pointless because the DB user is granted full permission anyway).
Contrast this code
mysqladmin -u root password "$ROOT_PASS"
with the "official" image:
"${mysql[@]}" <<-EOSQL
-- What's done in this file shouldn't be replicated
-- or products like mysql-fabric won't work
SET @@SESSION.SQL_LOG_BIN=0;
DELETE FROM mysql.user ;
CREATE USER 'root'@'%' IDENTIFIED BY '${MYSQL_ROOT_PASSWORD}' ;
GRANT ALL ON *.* TO 'root'@'%' WITH GRANT OPTION ;
DROP DATABASE IF EXISTS test ;
FLUSH PRIVILEGES ;
EOSQL
As a result:
$ docker run mariadb bash
$ scripts/start.sh &
$ mysql -h $(hostname) -u root
Welcome to the MariaDB monitor. Commands end with ; or \g.
It's due to the second line of the users table shown below. Note that 39264fcde276 was the randomly generated hostname for the docker container.
mysqld is the only process on localhost.
Unprivileged remote mysql users should not be able to spoof as localhost.
If they can, something has gone very wrong, and it's quite possible they
could bypass the mysql root password anyway.
It might still be useful to have a separate root user, and it doesn't look
like it hurts to leave it around.
Closes issue fedora-cloud#190.
I.e. loopback logins are possible without the root password. Logins from outside loopback are not permitted btw. So the root password we set up is pointless. (As well as the root user being pointless because the DB user is granted full permission anyway).
Contrast this code
with the "official" image:
As a result:
It's due to the second line of the users table shown below. Note that
39264fcde276
was the randomly generated hostname for the docker container.The text was updated successfully, but these errors were encountered: