Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd documentation about SOCKS connections and NetVMs #1041
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jul 2, 2015
Member
Whonix could help here? For example in Whonix-Workstation, TBB works out of the box without Tor over Tor. So does torchat. In Whonix-Workstation, by default there are listeners as if TBB was running and forwarding those SocksPort / ControlPort connections to the appropriate ports on Whonix-Gateway. Like to try if that works for you?
|
Whonix could help here? For example in Whonix-Workstation, TBB works out of the box without Tor over Tor. So does torchat. In Whonix-Workstation, by default there are listeners as if TBB was running and forwarding those SocksPort / ControlPort connections to the appropriate ports on Whonix-Gateway. Like to try if that works for you? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bnvk
Jul 2, 2015
@adrelanos thanks for the suggestion. I found a work around with my Pond config (and will add documentation). However, Whonix very well might have helped, I'm honestly a bit confused with how to use Whonix inside of Qubes and as to what end. I hope to better understand it at some point, but currently find their docs a bit cryptic.
bnvk
commented
Jul 2, 2015
|
@adrelanos thanks for the suggestion. I found a work around with my Pond config (and will add documentation). However, Whonix very well might have helped, I'm honestly a bit confused with how to use Whonix inside of Qubes and as to what end. I hope to better understand it at some point, but currently find their docs a bit cryptic. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jul 3, 2015
Member
Yes, this all needs improvement.
FYI:
Qubes OS Project gets OTF funding to integrate Whonix, improve usability:
http://blog.invisiblethings.org/2015/06/04/otf-funding-announcement.html
|
Yes, this all needs improvement. FYI: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bnvk
Jul 7, 2015
@adrelanos yah, i've heard, and it is very exciting :) I'm definitely up for better understanding / helping improve Whonix + Qubes integration and UX. If you ever want to ping me on IRC or Jabber feel free!
bnvk
commented
Jul 7, 2015
|
@adrelanos yah, i've heard, and it is very exciting :) I'm definitely up for better understanding / helping improve Whonix + Qubes integration and UX. If you ever want to ping me on IRC or Jabber feel free! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Does it still apply since #1201 ? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bnvk
commented
Oct 10, 2015
|
Probably not needed! Closing as such :-) |
bnvk commentedJul 2, 2015
There's an increasing number of apps that make opportune use of Tor by using a SOCKS connection if a user is running TorBrowser bundle. Of course, with Qubes + TorVM this is not needed. However, apps like the Pond messaging client require Tor to work. I could install and run Tor from within the Pond AppVM, but that is undesirable since i already have a Tor NetVM.
The issue i'm having is Pond is still unaware that traffic is being routed through Tor and says "Looking for a SOCKS proxy on port 9050 or 9150"
I have read over all the docs more than once, but either i'm missing something, or perhaps some other slight documentation about this sort of thing would be helpful :)