[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

controller GETINFO ns/id/fingerprint "s" record

To: or-talk@xxxxxxxxxxxxx
Subject: controller GETINFO ns/id/fingerprint "s" record
From: Wesley Kenzie <wkenzie@xxxxxxx>
Date: Wed, 21 May 2008 15:41:28 -0700
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Wed, 21 May 2008 18:42:18 -0400
Importance: Normal
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
Thread-index: Aci7k8vz+AiYPVHzS4q5Bx0kKQ9xgw==

What is the criteria for getting listed as an "Exit" node in the "s" record for the controller interface's GETINFO /ns/id/fingerprint?

I recently added accept *:443 to my ExitPolicy setting in torrc but it is not listed as an Exit node, and am wondering why not. The new ExitPolicy setting does show correctly in the GETINFO /desc/id/fingerprint data.

Also, where does the data originate from when the controller GETINFO command is used? Does it just grab data out of the cached* files on disk? Or poll one of the directory authorities? Or something else?

Wesley

Follow-Ups:
- Re: controller GETINFO ns/id/fingerprint "s" record
  - From: BarkerJr

Prev by Author: RE: most nodes now "not running" ?
Next by Author: RE: controller GETINFO ns/id/fingerprint "s" record
Previous by thread: Attacking the GPA-simulation scenario, point-by-point [Was: Re: Oh boy...]
Next by thread: Re: controller GETINFO ns/id/fingerprint "s" record
Index(es):
- Author
- Thread