| Summary: | mariadb 10.0.32 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | herman.viaene, lewyssmith, mageia, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA5-32-OK MGA5-64-OK advisory | ||
| Source RPM: | mariadb-10.0.31-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2017-08-17 23:33:07 CEST
Debian has issued an advisory for this today (August 17): https://www.debian.org/security/2017/dsa-3944 MGA5-32 on Asus A6000VM Xfce
Had to remove libdb develop package to be able to install maria, no further issues.
Before installing: stopped current mysqld, removed /var/lib/mysql
After installation at CLI:
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n] y
New password: <XXXXX>
Re-enter new password: <XXXXX>
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] n
... skipping.
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
Then used phpmyadmin to create a new table in the test database and dropped it again.
All seems OKWhiteboard:
(none) =>
MGA5-32-OK Installed and tested without issue. Don't have libdb installed. The tests consisted of using several scripts (e.g. wordpress), MySQL Workbench and a custom somewhat large SQL script to create a database with several tables, import data, calculate some statistics, and then delete the database. System: Mageia 5, x86_64, Intel CPU. # rpm -qa | grep mariadb | sort lib64mariadb18-10.0.32-1.mga5 lib64mariadb-embedded18-10.0.32-1.mga5 mariadb-10.0.32-1.mga5 mariadb-bench-10.0.32-1.mga5 mariadb-client-10.0.32-1.mga5 mariadb-common-10.0.32-1.mga5 mariadb-common-core-10.0.32-1.mga5 mariadb-core-10.0.32-1.mga5 mariadb-extra-10.0.32-1.mga5 mariadb-feedback-10.0.32-1.mga5 CC:
(none) =>
mageia Advisory from Comment 0. Validating at the same time, 2 OKs. Whiteboard:
MGA5-32-OK MGA5-64-OK =>
MGA5-32-OK MGA5-64-OK advisory An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2017-0289.html Status:
NEW =>
RESOLVED |