http://www.worldipv6launch.org/

((enjoy))

Exploit is in the wild! Be warned!

UPDATE: Apache 2.2.20 has been released and it fixes this vulnerability. Update ASAP!

Please note that on Ubuntu the fix has been backported to Apache 2.2.14-5ubuntu8.6 for 10.4 LTS, and 2.2.8-1ubuntu0.21 for 8.04 LTS.

((enjoy))

Ubuntu 11.10 looks really promising!

((enjoy))

Kernel Log: BIOS bugs behind greater power use – The H Open Source: News and Features.

((enjoy))

I’ve tested it on a Ubuntu 10.04 physical server, and here are some configuration hints.

Perl Modules

Use CPAN for installing required perl modules to use the device:

$ sudo apt-get install libusb-dev build-essentials
$ sudo cpan Bundle::CPAN
$ sudo cpan ExtUtils::MakeMaker
$ sudo cpan Inline::MakeMaker
$ sudo cpan Device::USB
$ sudo cpan Device::USB::PCSensor::HidTEMPer

then download a perl script from http://www.cs.unc.edu/~hays/dev/bash/temper/temper_mon.pl to use as a base for MRTG integration. Save the script in /usr/local/bin and modify it to print the data in the format good for MRTG, the last lines of the script should look like this:

foreach my $device ( @devices )
{
   say $device->internal()->celsius();
}
printf "0\n";
printf "fool\n";
printf "My Temper sensor\n";

MRTG Configuration

Simply add these lines to your mrtg.cfg to start graphing the temperature data:

Target[temper]: `/usr/local/bin/temper_mon.pl`
AbsMax[temper]: 50
MaxBytes[temper]: 30
Options[temper]: nopercent,growright,nobanner,nolegend,noinfo,expscale,gauge,noo
Title[temper]: My Server Room Temperature
PageTop[temper]: <h1>My Server Room Temperature</h1>
YLegend[temper]: Temperature C
ShortLegend[temper]: &nbsp;&deg;C
LegendI[temper]: Temperature &deg;C&nbsp;
ThreshMinI[temper]: 15
ThreshMaxI[temper]: 30
Unscaled[temper]: dwmy

If you want to use the MRTG threshold feature, add also these lines, and MRTG will send you email alert when the temperatures values are below or over the configured thresholds.

# Alert
ThreshDir: /var/mrtg/thresh
ThreshMailServer: smtp.example.com
ThreshMailSender: mrtg-alert@example.com
ThreshMailAddress[_]: supporto@example.com

Create the /var/mrtg/tresh directory to make MRTG happy. The Min Threshold is also used to detect if the sensor is unplugged since the program will read a value of 0.
It works like a charm!
((enjoy))

# /etc/init.d/zenoss-stack stop

# /etc/init.d/zenoss-stack start mysql

drop the "events" database

# /etc/init.d/zenoss-stack stop mysql

delete the ibdata1 and ib_log* files in the mysql data folder

# /etc/init.d/zenoss-stack start mysql

zenoss$ zeneventbuild localhost zenoss zenoss events

# /etc/init.d/zenoss-stack stop mysql

# /etc/init.d/zenoss-stack start

((enjoy))

The problem: the cloned Solaris guest will fail to boot, since for a still unexplained reason the PCI device mapping of the controller has changed and the kernel while booting will be unable to find the disk(s). This is really strange since VMware ESX should provide the same exact hardware to the guest, like in Linux OS guests.

Booting in failsafe mode and mounting the root file system on /a should show something like this:

The /devices/pci@0,0/pci15ad,1976/sd@0,0:a is the new device, while on /a/dev/dsk/c1t0d0s0 you can see the broken symlink to the wrong PCI path.

The solution: you have to reconfigure the devices inside the cloned guest; unfortunately for Solaris is far more complicated than in Linux OS.

1. Start the VM and at the grub prompt, enter fail-safe mode and allow the root file system to be mounted as read/write under /a.

2. Identify the new device name using the format command. In this case it is /pci@0,0/pci15ad,1976@10/sd@0,0 so replace where necessary from now on. vi may not display correctly so fix the terminal type with the following command:

5. Then edit /a/etc/vfstab (making a backup copy first) and modify the line mounting the root file system so instead of /dev/dsk/c1t0d0s0 and /dev/rdsk/c1t0d0s0 it reads the following absolute paths. Do not forget to suffix a: and ,raw respectively.

/devices/pci@0,0/pci15ad,1976@10/sd@0,0:a /devices/pci@0,0/pci15ad,1976@10/sd@0,0:a,raw / ufs 1 no -

6. Now we need to force a reconfiguration boot so that the system recreates the /etc/path_to_inst file that contains physical device to logical instance mappings. You can do this in 2 different ways: “touch /a/reconfigure” before reboot or at the grub prompt, I prefer to use grub.
Anyway it is time to restart:

# reboot

7. At the grub prompt, edit the grub entry thath sould automatically boot with ‘e’ and edit the kernel command line adding -r -s at the end of the line, then press ‘b’ to boot that entry. -r is to force reconfiguration, -s to start in single-user mode

8. Login and edit /etc/vfstab again so that you can replace those absolute paths for the / file system. If you have /var on a separate file system mount it manually to make vi happy. If you made a backup of this file before the last update, it would be easier to start with this. Before you do this use format to determine the new disks and update this file as appropriate. An example with the correct disk paths may be:

/dev/dsk/c3t0d0s1 – - swap – no -
/dev/dsk/c3t0d0s0 /dev/rdsk/c3t0d0s0 / ufs 1 no -
/dev/dsk/c3t0d0s7 /dev/rdsk/c3t0d0s7 /export/home ufs 2 yes -

9. Reboot again in multi-user mode and you’re done! System is now ready for use.
It seems that ZFS volumes will not be affected by the device reconfiguration, they should come up automatically.

YMMV.

Useful links:
- http://communities.vmware.com/message/907527
- http://rdiggle.blogspot.com/2010/06/using-solaris-1009-virtual-appliance.html

((enjoy))