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

Re: [tor-bugs] #28300 [Core Tor/Stem]: Scrolling support for tor-prompt is needed

#28300: Scrolling support for tor-prompt is needed
---------------------------+------------------------------
 Reporter:  wagon          |          Owner:  atagar
     Type:  enhancement    |         Status:  closed
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:  Tor: 0.3.4.8
 Severity:  Normal         |     Resolution:  wontfix
 Keywords:  tor-prompt     |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+------------------------------

Comment (by wagon):

 There is another question related to `tor-prompt` vs Nyx control
 interpreter. In `tor-prompt` double Tab key suggests possible completions
 for commands, but this doesn't work in Nyx interpreter. Can it be added to
 Nyx too? It is very convenient feature.

 Then, as concerns commands themselves, Nyx lists some outdated variants.
 For example, when I use `GETINFO status/version/num-concurring` and
 `GETINFO status/version/num-versioning` Tor writes to its log file:

 {{{
 [warn] status/version/num-concurring is deprecated; it no longer gives
 useful information
 [warn] status/version/num-versioning is deprecated; it no longer gives
 useful information
 }}}

 Should these commands be removed from interpreter's `/help GETINFO`
 listing?

 If `Sandbox 1` is set in `torrc`, during each start  Nyx does something
 inappropriate to Tor forcing it to complain in log:

 {{{
 [err] sandbox_getaddrinfo(): Bug: (Sandbox) failed to get address
 [hostname redacted]! (on Tor 0.3.4.9 )
 }}}

 Is it OK? Should it be fixed?


 There are many commands with `*` at the end. Does it always mean that some
 value must be substituted instead of `*`? For example, I didn't find any
 valid substitution for `GETINFO config/*` (`config/defaults` and
 `config/names` are separate and documented commands).

 In Nyx connections window the value `published` is printed as information
 about selected relay. What `ControlPort` command Nyx uses to get its
 value? `/var/lib/tor/cached-microdescs` file?

 Inverse situation is with Tor `version`: it is shown in `/var/lib/tor
 /cached-microdesc-consensus` but Nyx does not show it in information about
 relays (connections window). Can relay's Tor version be learned from
 `ControlPort` too?

 Yes, I could add [[https://nyx.torproject.org/#missing_relay_details|extra
 options]] to get more information accessible through Nyx and
 `ControlPort`, but my question is mainly about default Tor configuration.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28300#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs