Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 329
    • Issues 329
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #24343
Closed
Open
Issue created Nov 17, 2017 by David Goulet@dgoulet🐼Owner

Remove dead code and doc regarding the old SocksSocket option

In entry_connection_t, there is still is_socks_socket option that is simply not used.

Other place is this log which should be renamed to mention "Unix socket".

    log_info(LD_NET, "Closing SOCKS SocksSocket connection");

Finally, the man page is still listing the option within another option (although SocksSocketsGroupWritable is still a thing that we should probably rename).

       SocksSocketsGroupWritable 0|1
     If this option is set to 0, don’t allow the filesystem group to read and write unix sockets (e.g. SocksSocket). If the option
     is set to 1, make the SocksSocket socket readable and writable by the default GID. (Default: 0)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking