I'm not a web designer or a web developer! I'm a system administrator by nature and have a natural curiosity for things which lead to learning and some of this intarweb markup thingy.
As you seem to have found your way here somehow, here are some things I've done or have an interest in.
- OpenDNS 2012 Sysadmin Award
- Blog
- Me on Facebook
- Fuel Use - Android Market
- Fuel Use - Facebook
- Android Developer Stuff
- Torque Log Processing.
- Barrysplanet Gaming.
- Mad.4.wolF Game Server Stats.
- C.V.
| It's not all work! |
![]() |
Contact Details:
- Email - steve+website@null.stevewilson.co.uk
- MSN - steve_a_wilson@nullhotmail.com
- Google Talk - steve.a.wilson.74@nullgmail.com
- ICQ - 4037null2896
This page is best viewed in a web browser!
BOFH Excuse #161:
monitor VLF leakage
root> nmap -O -p22 107.21.186.38
Starting Nmap 5.21 ( http://nmap.org ) at 2013-05-18 20:51 BST
Nmap scan report for ec2-107-21-186-38.compute-1.amazonaws.com (107.21.186.38)
Host is up (0.033s latency).
PORT STATE SERVICE
22/tcp open ssh
No exact OS matches for host
Nmap done: 1 IP address (1 host up) scanned in 1.98 seconds
root> sshnuke 107.21.186.38 -rootpw="Z10N0101"
connecting to 107.21.186.38:ssh ... successful.
Attempting to exploit SSHv1 CRC32 ... successful.
Resetting root password to "Z10N0101".
System open: Access Level <9>
ssh -l root 107.21.186.38
root@107.21.186.38's password:
