Project

General

Profile

Feature #10058

Filter TorMonitor access to tor control socket

Added by alant about 4 years ago. Updated over 3 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/17/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Tor Monitor

Description

In Tails, TorMonitor should only have access to a safe subset of Tor control protocol.

To get the conversation between TorMonitor and the Tor daemon: sudo socat -v UNIX-LISTEN:/tmp/tor-control-copy UNIX-CONNECT:/var/run/tor/control.

Currently TorMonitor uses:

- PROTOCOLINFO
- AUTHCHALLENGE SAFECOOKIE
- AUTHENTICATE
- SETEVENTS
- GETCONF __owningcontrollerprocess
- GETINFO version
- SETEVENTS SIGNAL
- SETEVENTS CONF_CHANGED SIGNAL STREAM CIRC
- GETINFO circuit-status
- GETINFO stream-status
- GETCONF usemicrodescriptors
- GETINFO ip-to-country/*
- GETINFO ns/id/*


Related issues

Duplicates Tails - Feature #9001: Onion Circuits should connect via the Tor control port filter Resolved 03/03/2015

History

#1 Updated by alant about 4 years ago

  • Parent task set to #6842

#2 Updated by BitingBird about 4 years ago

  • Affected tool set to Tor Monitor

#3 Updated by intrigeri about 4 years ago

  • Status changed from New to Confirmed

#4 Updated by alant about 4 years ago

  • Duplicates Feature #9001: Onion Circuits should connect via the Tor control port filter added

#5 Updated by alant about 4 years ago

  • Status changed from Confirmed to Duplicate

#6 Updated by intrigeri over 3 years ago

  • Parent task deleted (#6842)

Also available in: Atom PDF