Active Topics

 


Reply
Thread Tools
Posts: 393 | Thanked: 67 times | Joined on Feb 2010
#11
Folks,

Doesn't the Tor application for the N900 somehow make use of a SOCKS proxy, all done via command line, and all transparent to the user?

Can we leverage that concept to set our own SOCKS proxy?
 
Posts: 38 | Thanked: 14 times | Joined on Feb 2010
#12
ok, this took me sometime to do but I finally managed to get fennec/firefox to use the socks proxy.

I'm not sure if I did anything special, but I was able to change the SOCKS port in about:config, once you highlight the option then press enter on the physical keyboard, it gives a window that doesn't seem to allow for any editing.

what I did was this : after pressing the enter button on the "network.socks.port" line in about:config, I "Did Not" click on the screen at all, I simply held down the right arrow on the keyboard to make sure I reached the end of the field, then pressed "backspace" a couple of times, and finally entered the new port (9966 in my case) and clicked the physical "enter" button on the keyboard to finish and it worked, this trick also works for the "network.proxy.type" which needs to be changed to "1", it's set to "5" originally.

on another matter,I've been trying to use tsocks, and my edited tsocks.conf file has the following entries :

local = 192.168.1.0/255.255.255.0

#default server
server = 212.117.160.44

Server_type = 5

Server_port = 9966 (the port I want to tunnel through)

now I'm confused : do I start the ssh tunnel from a terminal window (ssh -D...etc) then run "tsocks fennec" from another terminal ? or do I simply use the "tsocks fennec" command and it will be enough, and do I need to add a username for the server in the tsocks.conf file ?

any help would be appreciated, like I said I can use firefox by changing the settings in the about:config but I'd like to be able to use tsocks for other apps.

Last edited by ticktock666; 2010-03-01 at 13:50.
 
Posts: 393 | Thanked: 67 times | Joined on Feb 2010
#13
I would also like to use tsocks, I hope someone responds to the last poster...

thanks
 
Posts: 433 | Thanked: 274 times | Joined on Jan 2010
#14
set the tsocks.conf default server to 127.0.0.1 and the port to <yourPort>.

then start ssh socks proxy with
ssh -D <yourPort> user@server.

then run tsocks <yourApp> and tsocks will intercept comms and point them to your ssh.
 
Posts: 38 | Thanked: 14 times | Joined on Feb 2010
#15
thanks for the help, things working great now

any idea how to launch the facebook app using tsocks, I'm not very clear on the command & path to where the apps are installed.

cheers.
 
Posts: 433 | Thanked: 274 times | Joined on Jan 2010
#16
I assume you mean the facebook widget? sorry, no idea about that, though I assume that the widget spawns a separate process periodically to do an https session to the facebook server to fetch any updates, so if you can track down the call and it's possible to hack it to use tsocks then you are in luck?

Probably best to wait for someone who knows about how/where widget-created processes get launched on n900 to let you try to proxify it properly though :-)

Last edited by Pigro; 2010-03-02 at 14:03.
 
Posts: 38 | Thanked: 14 times | Joined on Feb 2010
#17
ok, tsocks is all fine and nice but I have been unable to launch the default browser using tsocks, I've tried "tsocks browser" but I get an error message :
invalid string constant "osso-combobox-entry-arrow", expected valid string constant

I'm not sure what this means but the terminal just hangs there until I Ctrl-C/kill it, what am I doing wrong here ?

I've also tried tsocks /usr/bin/browser and got the same error.
 
AMLJ's Avatar
Posts: 226 | Thanked: 59 times | Joined on Sep 2010 @ Mierlo, Netherlands
#18
I didn't know about this thread... You can get it working, without using tsocks or anything else... tsocks is fine, I use it for some things, but why use it when there are easier and better ways?

See a How-To on my blog:http://www.adelamlj.com/index.php?op...n900&Itemid=71
__________________
AMLJ**0-1-47
 
Posts: 116 | Thanked: 40 times | Joined on Mar 2010
#19
I have this working via SSH tunnel and do not have to enable/disable proxy in about:config ever.....this can be configured on a per connection profile via System, Settings, Internet Connections. This removes the need of having to change the 0 to a 1 in network.proxy.type each time you want proxy. My steps......

In microb:

In adddress bar go to about:config

change:

network.proxy.http_port to your chosen port
network.proxy.socks to localhost
network.proxy.socks_port to your chosen port above
network.proxy.ssl_port again your chosen port

Then under System, Settings, Internet Connections, Connections

find the connection you wish to use the proxy with.......then edit....next....next....advanced.....

Check Use Proxy
then ONLY fill in the fields for Port numbers for HTTP and HTTPS proxy with ....you guessed it your chosen port number.

You may want to scroll down and fill in the Do not user proxy for section with what makes sense to you.

Last......you need your ssh command. I highly suggest creating a public key for passwordless login to the host and embedding this command in a script. I call my script pxy and placed it in /usr/bin for a quick execution to establish my tunnel, my command is as follows:

ssh your remote host -p your remote port -l your remote username -nN -D your chosen local proxy port -o ConnectTimeout=5 NumberofPasswordPrompts=1 &

Hope this helps someone, I'll help where I can. I won't be watching this thread closely please feel free to PM for help. This works flawless for me. I suggest installing an alternative browser as well as they will not bide by the proxy settings in the event you need to authenticate with a captive portal unless you build the exception in the "Do not use proxy for" section of the Internet connection
 

The Following User Says Thank You to xopher For This Useful Post:
Posts: 11 | Thanked: 5 times | Joined on Aug 2010 @ RO
#20
Originally Posted by daperl View Post
This is not true. If you combine the following about:config settings with your ssh -D command, it works:

network.proxy.socks localhost
network.proxy.socks_port 3210
network.proxy.socks_remote_dns true
network.proxy.type 1

And remember, http://whatsyourip.org/ is your friend.

Why Nokia left the SOCKS fields out of the advanced network settings is a mystery to me, but there's a bug filed. Please vote for it; it's easy to find if you search for "proxy."

And as far as entering numbers in about:config: You can only get the dialog by selecting the field. and pressing the physical return key. Then, when the dialog comes up, close the keyboard and use the virtual keyboard. Bizarre, but it works.
He is right. I have tried his settings and it works.
The only different setting that i have is the port number wich is 7070 on me. but it works verry nice.
Nice one man
 
Reply


 
Forum Jump


All times are GMT. The time now is 19:37.