Fossil SCM
Clarify guidance regarding user 'nobody'
21e39ebe66a21b7…
· opened 11 years, 2 months ago
- Type
- Documentation
- Priority
- —
- Severity
- Cosmetic
- Resolution
- Fixed
- Subsystem
- —
- Created
- Jan. 26, 2015 6:09 p.m.
The Special Logins part of /setup_uedit says, "To disable universal access to the repository, make sure no user named 'nobody' exists or that the nobody user has no capabilities enabled." This sent me (a newbie) on a hunt for how to delete 'nobody', and eventually landing on the user docs: "Users can never be deleted..."
I adjusted the permissions instead and everything is fine, but I think the text about making sure a user doesn't exist should be removed, given that said user is created automatically and can't be deleted without low-level sqlite commands.
Comments (1)
The Special Logins part of /setup_uedit says, "To disable universal access to the repository, make sure no user named 'nobody' exists or that the nobody user has no capabilities enabled." This sent me (a newbie) on a hunt for how to delete 'nobody', and eventually landing on the user docs: "Users can never be deleted..."
I adjusted the permissions instead and everything is fine, but I think the text about making sure a user doesn't exist should be removed, given that said user is created automatically and can't be deleted without low-level sqlite commands.