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

Re: [tor-bugs] #10762 [Applications/TorBirdy]: TorBridy should try both SOCKS port 9050 and 9150

#10762: TorBridy should try both SOCKS port 9050 and 9150
-----------------------------------+------------------------------
 Reporter:  mikeperry              |          Owner:  ioerror
     Type:  defect                 |         Status:  needs_review
 Priority:  Medium                 |      Milestone:
Component:  Applications/TorBirdy  |        Version:
 Severity:  Normal                 |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+------------------------------
Changes (by jflory7):

 * severity:   => Normal


Comment:

 For what it's worth, there seems to be a few places in TorBirdy that
 aren't updated if the Tor port is changed. For example, when refreshing
 keys in Enigmail, the local proxy is hard-coded to 127.0.0.1:9150, which
 will always fail unless changed manually.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10762#comment:5>
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