Skip to content

GitLab

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

Closed
Open
Opened May 23, 2017 by Kali Kaneko@kaliOwner

refuse to run bitmask/bitmaskd if running as root

in previous releases of bitmask, we were aborting execution of the client if run by root. the reason is that we want to avoid users running bitmask with sudo, since it will mess with the settings by changing permissions of all the files that bitmaskd writes.

however, as a workaround for !113 (merged) I'm precisely relying on bitmask to be run as root for e2e tests. I think we need to capture this particular usage with some kind of flag (BITMASK_AS_ROOT or something like that).

Assignee
Assign to
Next
Milestone
Next (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: leap/bitmask-dev#8902