Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #12234

Closed (moved)
(moved)
Open
Created Jun 08, 2014 by Trac@tracbot

Add Option to ControlPort for SSL/TLS Support

I was thinking perhaps there should be an option to wrap the ControlPort socket in SSL. In the cases where TCP 127.0.0.1 or a Unix domain socket is used, this is admittedly of no value.

However, anywhere a remote TCP socket is allowed to interact with the tor ControlPort, we should probably have the option of encrypting the data (e.g. AUTHENTICATE and anything sensitive) while in transit over the network, where it could be subject to interception.

Interacting with the daemon could be done with openssl s_client if done by hand. The commonly-used controlport clients would have to enhanced as well to support use of SSL/TLS.

Without this, we'd have to stunnel or ssh tunnel this socket, implying those facilities were available on the host and/or platform.

Trac:
Username: blentz

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking