Chrome Firefox

Same Tabs behavior in Firefox like Chrome

I don’t like the default tabs behavior in Firefox. I hate to use the arrows to find not visible tabs. I prefer to see all open tabs although the tab is reduced with each new tab open. If I need to find a tab between many, I just move the cursor over each tab.

Well, there is a extension to this. The name is Prevent Tab Overflow, but for me is All Tabs Visible. I tested it and it works fine.

Yes, I’m a former Chrome user.


Chrome HTTP Proxy Linux Proxy

Force Chrome to tunnel DNS requests through a SSH socks proxy

On your local machine, make the SSH connection :

ssh -D 8888 server

Force Chrome to use the ssh tunnel for DNS requests :

google-chrome --proxy-server="socks5://localhost:8888"

You can check if it works by running this command on the ssh server :

tcpdump -i eth0 port 53

tcpdump will show dns trafic for any activity in Chrome.

Corkscrew HTTP Proxy Linux openSUSE Proxy ProxyCommand

SSH through HTTP proxies

I’m working with a client who only has a HTTP Proxy to output to Internet. It’s very restrictive but it works.

Under openSUSE 13.1 the browsers (firefox and chrome) work fine. The main problem comes when I try to do a SSH session to outside server.

The solution for me was to use Corscrew and the ProxyCommand.

I added the following line to ~/.ssh/config file:

ProxyCommand /usr/local/bin/corkscrew 80 %h %p

where is the proxy server and 80 is the port of the same proxy.

Optionally you can add a username/password for the HTTP Proxy.

ProxyCommand /usr/local/bin/corkscrew 80 %h %p ~/.ssh/proxyauth

Your login credentials should be in ~/.ssh/proxyauth in format:




Gnome Linux openSUSE

How to disable touchpad tapping when typing on keyboard

After I installed openSUSE 13.1 on a Dell Inspiron 5537 I had problems with the video to have the max. resolution 1366×768. The YaST just recognized 1024×768. I had to create a /etc/X11/xorg.conf file (if it doesn’t exist) and to add specific custom modelines. Here my file /etc/X11/xorg.conf:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Modeline "1366x768" 76.75 1366 1414 1446 1618 768 771 776 790 +hsync -vsync
Modeline "1366x768" 51.16 1366 1414 1446 1618 768 771 776 790 +hsync -vsync

After I restarted the X server I got the correct resolution.

Another thing I had problems was the TouchPad, when I used the keyboard but if I tap the touchpad accidentaly the cursor was moved. I fixed it on Gnome-Control-Center->Mouse & Touchpad, uncheck “Tap to click” and check “Disable while typing”. With both options checked the behaviour is that the touchpad keeps working.



Firefox Proxy SOCKS

DNS resolves locally on SOCKS Proxy on Firefox

A tunnel SSH SOCKS is a great way to quickly tunnel web traffic. But there is a problem. The DNS requests are still trying to connect locally instead to use the SSH tunnel.

Luckily, with SOCKS5 Firefox can control which side of the proxy handles DNS lookups. By default, it does the lookups locally resulting in the scenario above. To change this, set network.proxy.socks_remote_dns = true in about:config. This makes the SOCKS proxy more like a regular proxy, where DNS is handled by the remote machine end of the tunnel. Do the following for this:

In the browser location bar (the place where you type web addresses), type about:config and press [Enter]. This opens a different set of Firefox preferences. Where it says ‘Filter:’ at the top, type network.proxy.socks. The list of preferences will automatically change to show your proxy preferences. Highlight ‘network.proxy.socks_remote_dns’ by clicking it only once. Then, right-click it. This opens a small pull-down menu. Select ‘Toggle’ from the menu to change its value from ‘false’ to ‘true’.

Close Firefox and restart it.