You are not logged in.
Has anyone else tried to to use chromium with tsocks? I thought it would be transparent and work fine, but it doesn't seem to work at all. I just get error messages that chromium can't load the web page, but no site errors. I've tried both by setting LD_PRELOAD and by running 'tsocks chromium-browser' with an existing /etc/tsocks.conf that works perfectly with other applications (mutt,irssi, pacman, etc.). Is this just a chromium bug? Anyone else care to test this?
Thanks!
Scott
Last edited by firecat53 (2010-01-07 17:00:49)
Offline
LD_PRELOAD wont work due to chromium's sandboxing.
Offline
Is there a way to get it to use my socks proxy, then? I didn't understand the documentation (what little there was), and clicking the proxy settings button in the options just opens my browser to a google wiki page on ssl certs??? .
Thanks,
Scott
Offline
Its best to set the proxy with an env var. See "man chromium". The current proxy configuration is just broken if you are not using Gnome.
Offline
don't forget that you could use privoxy and then set the chromium network options to use a proxy
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
So what would the correct course then be for a socks tunnel set up on port 3456 of localhost: ? (setup with ssh -fND 3456 homeserver)
export SOCKS_VERSION=5
chromium-browser
That doesn't work, but I can't figure out what else to set.
Thanks!
Scott
Offline
you have to set SOCKS_SERVER aswell as SOCKS_VERSION
i.e.
export SOCKS_SERVER=yourSocksServer:yourPortOffline
EDIT: I should have had SOCKS_VERSION=4 or just left it alone for the default of 4. Works as expected now.
I have a computer ($BG) with sshd open on port 81.
from my .bashrc
function unblock() {
port=5432
export SOCKS_SERVER=localhost:$port
export SOCKS_VERSION=5
chromium &
ssh -p 81 -D $port $BG
}"unblock" brings chromium up but with no change in it's behavior. It's not using SOCKS.
ENVIRONMENT
Chromium obeys the following environment variables:all_proxy
Shorthand for specifying all of http_proxy, https_proxy, ftp_proxyhttp_proxy, https_proxy, ftp_proxy
The proxy servers used for HTTP, HTTPS, and FTP. Note: because Gnome/KDE proxy settings may propagate into these variables in some terminals, this variable is ignored (in preference for actual system proxy settings) when running under Gnome or KDE. Use the command-line flags to set these when you want to force their values.auto_proxy
Specify proxy autoconfiguration. Defined and empty autodetects; otherwise, it should be an autoconfig URL. But see above note about Gnome/KDE.FILES
The man page does not mention any SOCKS_* settings.
However, wrench icon->options->Under the Hood: Network (Change proxy settings) launches about:linux-proxy-config which does.
SOCKS_SERVER: SOCKS proxy server (defaults to SOCKS v4, also specify SOCKS_VERSION=5 to use SOCKS v5)
Version : 5.0.375.55-1
Am I doing it wrong?
Last edited by _will (2010-06-09 15:39:40)
Offline