Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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
  • #6907

Closed
Open
Created Sep 21, 2012 by Trac@tracbot

arm simply assumes it is connecting to a local tor instance (which is not necessarily always the case)

It looks like arm simply assumes to connect to a local tor instance:

  • the hostname and kernel version displayed in arm's interface is not from the relay (it is from localhost).

The following warnings are also caused by this assumption:

[ARM_WARN] The torrc differs from what tor's using. You can issue a sighup to reload the torrc values by pressing x.
   - torrc values differ
[ARM_WARN] Unable to read tor's log file: /var/log/tor/log on lines: 2, 3, 4, 6, 7, 8, 9, 10

Maybe arm could try to detect if it is connecting to a local tor instance by comparing the IP from the '-i' parameter with locally configured IP adresses? An alternative method and probably easier and more reliable: If the pid (gathered via 'GETINFO process/pid') does not match one of the pids returned by 'pidof tor' it is probably not a local tor instance.

What do you think?

Trac:
Username: cypherpunkx

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