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

[Tor Bug Tracker & Wiki]

#10762: TorBridy should try both SOCKS port 9050 and 9150
---------------------------+---------------------
     Reporter:  mikeperry  |      Owner:  ioerror
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:
    Component:  TorBirdy   |    Version:
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |
---------------------------+---------------------

Comment (by Viggy_prabhu):

 I have fixed this bug by adding a check for testing if TOR Daemon is
 running by just trying to connect to port 9050. If so, then it uses port
 9050, else it just sticks to port 9150.
 The fix is in the branch "fixingDefaultTorPort" here,
 https://github.com/viggyprabhu/torbirdy/tree/fixingDefaultTorPort
 Please let check it and let me know if something needs to be modified.

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