Archive for maio \10\UTC 2010|Monthly archive page

Como ativar acesso SSH no ESX 4.0

Por padrão o esx 4.0 vem com o acesso de root via ssh desabilitado! veja como habilitar neste link em inglês!

01.) First you must login as a root at the console of your ESX 4 Server.

02.) Then you must navigate to the /etc/ssh directory. Just type in:  cd /etc/ssh

03.) Open nano (text editor, easy to use…) type: nano sshd_config

Navigate to the line saying PermitRootLogin no and change it to Yes.

04.) Type then CTRL+X to exit. On the prompt answer Y (as Yes to save the modified file).

05.) Then you’ll need to restart the sshd service typing: service sshd restart.

06.) While you are in the cosole just type in the following two commands to open firewall ports:

esxcfg-firewall -e sshServer
esxcfg-firewall -e sshClient


svchost viewer


Project Description
A program to see what all those svchost.exe are running.

Ever wondered what all those svchost.exe processes are running ?? Well here is an app
to tell you, it gives you some basic information like the Name and description.

– No installation required.
– Only requirement is that you have .net installed (ver 2.0 or newer).
– Work in Windows XP (sp2) and Vista and Windows 7(Beta).
– Coded in C#


Transformando o windows 7 e o 2k8 em um Wifi Hot Spot

Desenvolvido por Chris Pietschmann

The Wireless Network create/shared with Virtual Router uses WPA2 Encryption, and there is not way to turn off that encryption. This is actually a feature of the Wireless Hosted Network API’s built into Windows 7 and 2008 R2 to ensure the best security possible.

You can give your “virtual” wireless network any name you want, and also set the password to anything. Just make sure the password is at least 8 characters.


Entendendo ataques Man in the middle

Exelente matérial sobre ataques man in the middle escrito por Chris Sanders’

Understanding Man-in-the-Middle Attacks – ARP Cache Poisoning (Part 1)

Understanding Man-In-The-Middle Attacks – Part2: DNS Spoofing

Understanding Man-In-The-Middle Attacks – Part 3: Session Hijacking