Issue Details (XML | Word | Printable)

Key: MDL-14176
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Peter Bulmer
Reporter: Valery Fremaux
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Moodle

Admin loses control of moodle - mnet related

Created: 04/Apr/08 06:46 AM   Updated: 26/Oct/09 12:16 PM
Return to search
Component/s: Authentication, Networking
Affects Version/s: 1.8.4
Fix Version/s: 1.8.11, 1.9.7

Database: MySQL
Participants: Luke Hudson, Peter Bulmer and Valery Fremaux
Security Level: None
Affected Branches: MOODLE_18_STABLE
Fixed Branches: MOODLE_18_STABLE, MOODLE_19_STABLE


 Description  « Hide
Here is a case where legacy admin can lose completely control of the running Moodle :

As reconsidering mnet host table when recording peers after renewing the mnet_localhost_id in configuration, (problem of generating public key on Moodle 1.8.1 upgraded to 1.8.4), the mnet_hosts had a rotated id generated by an auto-increment, setting known hosts to 3, 4, 5 (regenerated once).

The issue is that mnethostid field of all user accounts has not been updated equally.

Admin account (id = 1) loses control and access in Moodle because forced manual account, and his mnethostid remained set to 1.

The mnet environement regeneration process should consider rekeying all mnethostsid of manual uses to the newly generated mnetlocahost id.
 

 All   Comments   Change History   Version Control      Sort Order: Ascending order - Click to sort in descending order
Luke Hudson added a comment - 29/May/08 12:45 PM
Changed 'looses' to correct 'loses'. No offense intended.

Peter Bulmer added a comment - 04/Mar/09 07:18 AM
Hi Valery,
For the benefit of those reading the bug report, can you develop a little on what you mean by:
"As reconsidering mnet host table when recording peers after renewing the mnet_localhost_id in configuration, (problem of generating public key on Moodle 1.8.1 upgraded to 1.8.4), the mnet_hosts had a rotated id generated by an auto-increment, setting known hosts to 3, 4, 5 (regenerated once)."

In particular if you could describe the steps needed to reproduce this problem that would possibly be helpful