[tor-bugs] #28921 [Core Tor/Stem]: tor-prompt command 'GETINFO desc/all-recent > /dev/null' fails

[Tor Bug Tracker & Wiki]

#28921: tor-prompt command 'GETINFO desc/all-recent > /dev/null' fails
---------------------------+-----------------------------------
 Reporter:  wagon          |          Owner:  atagar
     Type:  defect         |         Status:  needs_information
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:  descriptor     |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+-----------------------------------

Comment (by wagon):

 Replying to [comment:3 atagar]:
 > Hi wagon. This is odd, I'm having difficulty reproducing that
 stacktrace. Non-ascii content appears on the contact lines but this is
 normal and stem accounts for this...
 >
 > {{{
 > grep -P "[\x80-\xFF]" cached-descriptors
 > }}}
 Your grep doesn't catch all non-ascii characters. For example, I tried
 [[https://stackoverflow.com/questions/14567745/detect-russian-characters-
 with-grep|this suggestion]] and found the following:
 {{{
 $ grep -E "[А-Яа-яЁё]" cached-descriptors
 contact ++Питер++ c.m.i(at)mail.ru    ++ hkp://keyserver.ubuntu.com:11371
 ++ Bitcoin?  153gfzos233LcSnJpDF5u3q76iVAACwTAd
 }}}
 I have no idea what are the characters which results to error.

 > I tried parsing this through stem and printing the output with both
 python 2.7 and 3.5 but couldn't repro that stacktrace. Are you using the
 copy of stem from git? If not then please give that a whirl.
 I used
 [[http://trac.torproject.org/projects/tor/ticket/28332#comment:7|this git
 version]]. Now I've found another interesting observation. `tor-prompt`
 from 1.6.0 (release) doesn't have this problem.

 > There are no privacy issues with this file. It's just cached descriptor
 content. Everyone receives the same and each hours descriptors are
 publicly available on CollecTor.
 There are privacy issues with this file, because IP addresses in
 annotations `@source` are guard nodes your Tor uses. I don't think it is
 safe to tell everybody which guard nodes you are using now.

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