Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #27334

Closed (moved)
Open
Created Aug 26, 2018 by Trac@tracbot

RelaxDirModeCheck on ControlSocket still requires group to m

Even with RelaxDirModeCheck flag on the ControlSocket tor requires the folder (containing the socket file) group to match the group of the user running tor.

Could you lift this requirement when the RelaxDirModeCheck flag is given or is there an important reason for that?

os: FreeBSD 11.2

conf:

ControlSocket /var/run/tor-instances/123/controlsocket GroupWritable RelaxDirModeCheck

log:

Before Tor can create a control socket in "/var/run/tor-instances/123/controlsocket", the directory "/var/run/tor-instances/123" needs to exist, and to be accessible only by the user and group account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)

Trac:
Username: a_p

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None