MariaDB is just a fork of MySQL so the code is the same. Over time it will diverge but under control of the community rather than Oracle. On 08/31/2014 12:43 AM, Tim Dunphy wrote: >> my.cnf doesn't have the passwords. When you first set up mysql, you use >> the mysqladmin command to set the root password. >> MariaDB doesn't handle the initial set up any differently than MySQL. >> man mysqladmin >> C7 does do some stuff differently with the config as the "real" config >> files are in /etc/my.cnf.d /etc/my.cnf includes those files to build a >> config. > > Cool thanks. That worked! I was going in with the initial login with no > password prompt and setting up the root user with the 'create user' > command which didn't work. The traditional mysql approach did. Thanks > again! > > > On Sat, Aug 30, 2014 at 11:44 PM, Steven Stern < > subscribed-lists at sterndata.com> wrote: > >> On 08/30/2014 10:12 PM, Tim Dunphy wrote: >>> Hello, >>> >>> I discovered today that CentOS 7 has replaced MySQL with MariaDB. Which >> is >>> fine, it's seems really similar. And I was already aware that it was >>> written by the original team that wrote mysql. >>> >>> It's cool that the mysql command still gets you in! >>> >>> This is the version I have: >>> >>> [root at web1:~] #mysql --version >>> mysql Ver 15.1 Distrib 5.5.37-MariaDB, for Linux (x86_64) using readline >>> 5.1 >>> >>> But for some reason all I have to do is type the word 'mysql' to get me >>> into the database. >>> >>> That's ok for initial setup I guess. But once I was in a did away with >> all >>> the accounts that either had blank set for the username, and updated all >>> the accounts to use passwords. >>> >>> MariaDB [mysql]> select User,'@',Host,Password from user; >>> +-------+---+-----------+-------------------------------------------+ >>> >>> | User | @ | Host | Password | >>> >>> +-------+---+-----------+-------------------------------------------+ >>> >>> | root | @ | localhost | *8328225AE4A663FAKEFAKEFAKEFAKEFAKE93D61 | >>> >>> | root | @ | web1 | *8328225AE4A663FAKEFAKEFAKEFAKEFAKE93D61 | >>> >>> | root | @ | 127.0.0.1 | *8328225AE4A663FAKEFAKEFAKEFAKEFAKE93D61 | >>> >>> | admin | @ | localhost | *8328225AE4A663FAKEFAKEFAKEFAKEFAKE93D61 | >>> >>> +-------+---+-----------+-------------------------------------------+ >>> >>> 4 rows in set (0.00 sec) >>> >>> I also did a search from root to find any my.cnf files and didn't find >> any >>> that has user accounts in them. >>> >>> Also I find that for the root accounts I can't seem to login even if I >> set >>> the password in the database without encryption and copy/paste the >> password >>> into the prompt. >>> >>> However the non-root account (admin) does let you in with the password. >>> >>> So I'm wondering how to secure mariadb so that it doesnt' let you in >>> without typing in a username and password and also why it doesn't let you >>> log in as 'root'? Is the root account disallowed from logging in by >> default? >>> Thanks >>> Tim >>> >> >> my.cnf doesn't have the passwords. When you first set up mysql, you use >> the mysqladmin command to set the root password. >> >> MariaDB doesn't handle the initial set up any differently than MySQL. >> >> man mysqladmin >> >> C7 does do some stuff differently with the config as the "real" config >> files are in /etc/my.cnf.d /etc/my.cnf includes those files to build a >> config. >> >> >> >> -- >> -- Steve >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > > > -- > > > ********************************************************* > David P. Both, RHCE > Millennium Technology Consulting LLC > 919-389-8678 > > dboth at millennium-technology.com > > www.millennium-technology.com > www.databook.bz - Home of the DataBook for Linux > DataBook is a Registered Trademark of David Both > ********************************************************* > This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. >