| Summary: | moodle new security issues fixed in 2.8.9 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | major | ||
| Priority: | Normal | CC: | davidwhodgins, sysadmin-bugs, wilcal.int |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://lwn.net/Vulnerabilities/666962/ | ||
| Whiteboard: | has_procedure MGA5-32-OK advisory | ||
| Source RPM: | moodle-2.8.8-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2015-12-03 14:32:54 CET
Testing procedure: https://bugs.mageia.org/show_bug.cgi?id=10136#c3 Whiteboard:
(none) =>
has_procedure Working fine on our production Moodle server at work, Mageia 5 i586. Whiteboard:
has_procedure =>
has_procedure MGA5-32-OK In VirtualBox, M5, KDE, 64-bit Package(s) under test: moodle default install of moodle [root@localhost wilcal]# urpmi moodle Package moodle-2.8.8-1.mga5.noarch is already installed To get this up and running simplest way: urpmi mariadb systemctl enable mysqld.service systemctl start mysqld.service mysql -u root mysql> create database moodle; mysql> create user 'moodle'@'localhost' identified by '<test>'; mysql> grant all on moodle.* to 'moodle'@'localhost'; mysql> ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci; mysql> exit; Then in an su - terminal kwrite /var/www/moodle/config.php and in the empty single quotes for dbuser and dbpass, put 'moodle' for dbuser ( line 11 ), and the password 'test' ( line 12 ) used to create user mysql command in for dbpass. All went as expected. stop then restart mysqld Then browse to http://localhost/moodle to complete the setup. "Unable to connect" on Firefox browser. http://localhost/~wilcal/ works fine on the same browser. I still get this. Hints? CC:
(none) =>
wilcal.int I think that means unable to connect to the database. If your commands were exactly what you typed, when you created the user in mysql, it should have been "identified by 'test';" without the <>. (Or perhaps you could put the password as <test> in config.php, that might work too).
Dave Hodgins
2015-12-05 03:30:58 CET
Keywords:
(none) =>
validated_update An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2015-0464.html Status:
NEW =>
RESOLVED
David Walser
2015-12-07 17:06:02 CET
URL:
(none) =>
http://lwn.net/Vulnerabilities/666962/ |