Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Synchronet Synchronet
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 185
    • Issues 185
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Main
  • SynchronetSynchronet
  • Issues
  • #361

Closed
Open
Created Mar 03, 2022 by Andre Robitaille@andreMKEContributor

Remove code co-sysop flags and exemption checks

I'm unable to make tests work where this code actually performs as expected, where a co-sysop can edit a higher-level sysop only if they have that flag/exemption themselves.

In my opinion:

  1. The BBS world is past the point of needing this.
  2. A co-sysop shouldn't be able to add flags/exemptions to a user of any security level if they don't have it themselves.
  3. A co-sysop shouldn't be able to add flags/exemptions to their own account

But mostly just 1 above. I don't think we need this anymore, and the code should just be simplified to a co-sysop cannot edit a security level above their own, no exceptions.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking