Monday, June 9, 2008

Process Explorer for Windows

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you'll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you'll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

http://www.google.com/search?q=Process+Explorer

OSWA-Assistant Wireless Hacking ISO

The OSWA-Assistant is a no-Operating-System-required standalone toolkit which is solely focused on wireless auditing. As a result, in addition to the usual WiFi (802.11) auditing tools, it also covers Bluetooth and RFID auditing. Using the toolkit is as easy as popping it into your computer's CDROM and making your computer boot from it!

http://oswa-assistant.securitystartshere.org/

Tuesday, May 20, 2008

A Study of Passwords and Methods Used in Brute-Force SSH Attacks

Quite interesting paper talking about the ever-increasing problem of ssh brute-force attacks:

http://people.clarkson.edu/~owensjp/pubs/leet08.pdf

Sunday, April 27, 2008

'yum-protectbase' vs. RHN

I can't seem to get 'yum-protectbase' to behave correctly with RHEL5's rhnplugin. From `rpm -qi yum-protectbase`:

Description :
This plugin allows certain repositories to be protected. Packages in the protected repositories can't be overridden by packages in non-protected repositories even if the non-protected repo has a later version.

The problem is that, the RHN repositories aren't defined by standard files in '/etc/yum.repos.d/' so I can't add 'protect=1'. The same problem is documented here and here.

[EDIT]: This bug has now been fixed. See my comments on this post for details.

Wednesday, April 23, 2008

Dmidecode - print hardware information from your BIOS

Dmidecode reports information about your system's hardware as described in your system BIOS according to the SMBIOS/DMI standard (see a sample output). This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).

Monday, April 21, 2008

Cross-subnet booting of HP-UX

The following link describes how to set up an HP-UX 11i box as a "Boot-Helper System":

http://docs.hp.com/en/5992-3336/apds01.html

swinstall a specific version

Here's how to swinstall a specific version of a depot, product or fileset:

swinstall -s ignite:/swdepot/Ignite/IgniteUX Ignite-UX.BOOT-KRN-11-11,r=C.6.8.152

Then verify it:

swlist -l fileset -a state Ignite-UX.BOOT-KRN-11-11