Prevent registration of accounts under protected names
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Certain account names like "security", "info", "admins", etc. shouldn't be registrable to avoid confusion. (That said, security has already been registered, by me as a sysadmin, to facilitate creation of the security-discuss mailing list. But sysadmins ought to be trusted not to misuse the name for other things, like posing security@ as a security contact address for the SRCF...)
Given that group account creation is subject to manual review, there is already a layer of prevention that should stop such names being taken. It would be better if the set of "reserved" account names is programmatically enforced by our systems, though.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the account and group creation paths in the Python library and identify where names are validated or manual review is enforced. Define the protected-name behavior, including how the existing security account is handled, and add or update tests showing that reserved names cannot be registered while permitted accounts still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100