Open Bug 320177 Opened 19 years ago Updated 10 years ago

Impersonated (sudo) updates should be logged

Categories

(Bugzilla :: Administration, task)

2.21
task
Not set
normal

Tracking

()

People

(Reporter: kbenton, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [wanted-bmo])

Bug 204498 introduces the ability to impersonate others in the database, however, no mechanism was implemented to log that a person was being impersonated in the logs. The UI should not allow a malicious administrator to frame another user without leaving evidence behind of what was done. We can't stop admins from hacking the DB manually, but we sure can do a lot to make it harder for them to hack with mallicious intent from the UI. While this is being done, it seems that making impersonation a param that can only be turned on from the localconfig parameters seems to be a wise idea. That way, only those with shell access to the system can turn impersonation on.
You report two things here: - logging sudoers; - having a param in localconfig to turn sudo sessions on or off. I don't like the idea of this param in localconfig. I prefer a parameter accessible from editparams.cgi. But I fully agree about logging sudoers.
OS: Windows XP → All
Hardware: PC → All
(In reply to comment #1) ><<<snip>>> > But I fully agree about logging sudoers. > In that case, let us leave this bug as is with its current title, so this bug can be used to track the implementation of logging of actions performed during an sudo session. I should note that most of the places where logging can be inserted are already noted in the code.
No longer blocks: 204498
Blocks: 338200
Blocks: 142736
Summary: Impersonated updates should be logged. → Impersonated (sudo) updates should be logged
Whiteboard: [wanted-bmo]
Severity: normal → enhancement
Depends on: 328904
Target Milestone: --- → Bugzilla 4.4
Too late for 4.4. We already released rc1.
Target Milestone: Bugzilla 4.4 → ---
Target Milestone: --- → Bugzilla 5.0
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.