| Summary: | mariadb several new security issues | ||
|---|---|---|---|
| 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: | davidwhodgins, herman.viaene, sysadmin-bugs |
| Version: | 5 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA5-32-OK | ||
| Source RPM: | mariadb-10.0.33-2.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2018-02-16 20:04:20 CET
MGA5-32 on Dell Latitude D600 Xfce No installation issues. This was an update on an existing previous version. Using phpmyadmin, I couls delete a previous test database, create a new one, create a table and populate it some data. All OK. Whiteboard:
(none) =>
MGA5-32-OK Advisory committed to svn. Validating the update based on above test. Keywords:
(none) =>
advisory, validated_update An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2018-0139.html Resolution:
(none) =>
FIXED |