Category: internet

config para rede4 / optimus
Name: Optimus
APN: internet
Server: *
MCC: 268
MNC: 03
APN Type: default

config para TMN / uzo
Dados Móveis:
Nome de Utilizador: Em branco
Palavra-passe: Em branco

Nome de Utilizador: vas
Palavra-passe: vas
MMSC: http://mms/servlets/mms
Proxy de MMS:
MMS – Tamanho Máximo

great post about using rtorrent by K. Mandla


Aria2 commands

Aria2 is available here

Download from WEB

Download from 2 sources

BitTorrent Magnet URI

$ aria2c ‘magnet:?xt=urn:btih:248D0A1CD08284299D

Download URIs found in text file

$ aria2c -i uris.txt

mais info aqui.

wireless network cards – modes

conheço os seguintes modos de funcionamento de placas wireless:

i) managed – permite às placas estarem activas, emitindo e recebendo packets e ligações a redes
ii) monitor – modo passivo em que a placa apenas recebe info.

o comando para alternar entre estes dois modos é:

sudo iwconfig wlan0 (ou eth1, etc) mode monitor (ou managed)

If, like me, you’ve decided to dump for maybe you find this interesting. II ‘ve found a couple of scripts that allow me to dump the database and import it to

Thats quite usefull for those, like me, who have used for years now.

here’s the link to those scripts

despite being a very, very new service it’s spreading like wildfire in cyberspace. Specially in free software and open source communities, due to social tools as

Altough the service already supports a bunch of media players, it doesn’t officially supports my favorite player: banshee. That problem has been overcome today with the help of the online community.

the solution is  quite simple. just edit /etc/hosts and add the following line:

linux outlaws podcast

my little contribution in answer to this post. later i’ll print it out a copy to post somewhere.

How To Set Up SSH With Public-Key Authentication On Debian Etch

Preliminary Notes

This mini-howto explains how to set up an SSH server on Debian Etch with public-key authorization (and optionally with disabled password logins). SSH is a great tool to control Linux-based computers remotely. It’s safe and secure.

There’s no warranty that it’ll work for you. All of these settings are applicable for Debian and -like systems! There may be slightly changes on other systems as well.

Installing SSH On The Server

First, we install the SSH on our server. We can do that with this command: (Note that you must be root to do that!)

apt-get install ssh

Preparations On Our Client (Desktop) System

Second, we take some preparations on our desktop machine. This PC will be used to connect the server. So, the SSH-server has been installed on a different machine. On your desktop machine, we install the ssh client (which we use to connect the server). Note that installing programs requires root privilege! If you’re not logged in as root, please log in! (su root then type your password.) Then install the client:

apt-get install openssh-client

Switch back to your normal user (not root, respectively). Then type these commands in order:

mkdir ~/.ssh
chmod 700 ~/.ssh
cd ~/.ssh

We generate our key-pair, a public-key and a private-key. The public-key will be placed on the server, and you will log in with your private-key. When asked, type your passphrase (it’ll be needed for future logins, so remember it!):

ssh-keygen -t rsa -C “A comment… usually an email is enough here…”

Then we copy the public key (which we’ve generated just before) to our (remote) server. The remoteuser should not be root! Choose the default non-root user as remoteuser. (Note the colon at the end of the line! It’s important.)

scp -p remoteuser@remotehost:

Then we log in with SSH, and we copy the public key to its right place:

ssh remoteuser@remotehost
mkdir ~/.ssh
chmod 700 ~/.ssh
cat >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
mv ~/.ssh

We have to delete the public key on the desktop, because otherwise the SSH client doesn’t allow us to log in to the server. So, type this command:


And then we log back:

ssh remoteuser@remotehost

If we’ve done everything precisely as detailed above, then you’ll be asked for the passphrase. Type it, then you are in and have a fairly safe SSH-environment!

Disabling Password Authentication

Disabling it is a good way to have a safer SSH-installation. Then you can log in only with a key-pair, so be careful not to lose it! It’s purely optional but safe to activate! But before doing it, please make sure that key-based authentication is working out-of-the-box. Sit down in front the server (so don’t log in remotely as we have to restart the SSH later…) and type these commands manually as root:

cd /etc/ssh
cp sshd_config sshd_config.orig
nano sshd_config

You will have the nano text-editor on screen open with the main SSH configuration file. Change these lines (don’t bother if any of these lines have a ‘#’ mark at the beginning; if they have, just delete the hashmark as well):

PermitRootLogin		yes
PasswordAuthentication	yes
UsePAM			yes

To these:

PermitRootLogin		no
PasswordAuthentication	no
UsePAM			no

Then save the file with Ctrl + O , and restart the SSH server:

/etc/init.d/ssh restart

Be careful: if you disable password authentication, then you won’t be able to log in with passwords! Only key-based authentication will be available.

full credits on this tutorial go to howtoforge

Sometimes it’s useful to tunnel all web traffic over SSH, without having to start Firefox on a remote computer. For example, to work around network monitoring or snooping, or to avoid badly configured routers on the Internet. If you can change the settings on your web browser, you can probably use SSH to circumvent these filters.

SOCKS is a protocol is used by some proxy servers. The SOCKS protocol allows a client (such as a web browser) to ask a server to download a file for it, rather than downloading the file directly. Most SSH clients can act as a SOCKS proxy server, securely tunnelling requests through your SSH session, making an ordinary (insecure) web request from your Ubuntu computer.

Using the command-line SSH client, you should activate SOCKS by doing:

ssh -C -D 1080 user@host

-D refers to Dynamic port forwarding, and 1080 is the standard SOCKS port. You can use a different port if you prefer, but you should choose a port in the range 1024 to 49151, inclusive.

-C enables Compression, which speeds the tunnel up when proxying mainly text-based information (like web browsing), but can slow it down when proxying binary information (like downloading files).

There is also a brief discussion in the PuTTY manual page about how to get PuTTY to act as a SOCKS proxy server.

Once you have set your SOCKS proxy up, your applications can use a SOCKS proxy on the computer you are connecting from. For example, in Firefox:

  • go to Edit -> Preferences -> Advanced -> Network -> Connection -> Settings…

  • check “Manual proxy configuration”
  • make sure “Use this proxy server for all protocols” is cleared
  • clear “HTTP Proxy”, “SSL Proxy”, “FTP Proxy”, and “Gopher Proxy” fields
  • enter “” for “SOCKS Host”, and “1080” (or whatever port you chose) for Port.

You can also set Firefox to use the DNS through that proxy, so even your DNS lookups are secure:

  • Type in about:config in the Firefox address bar
  • Find the key called “network.proxy.socks_remote_dns” and set it to true

The SOCKS proxy will stop working when you close your SSH session. You will need to change these settings back to normal in order for your browser to work again.