Indeed the blog post is quite informative.
Since this is a ilbc hack, it would seem that docker would be a great way to detect this, since you can get a different libc.
Running: `docker run -P -it -v /:/mnt ubuntu`
gives you a root shell under a different libc with all of your filesystems mounted under /mnt
This is of course speculation since I assume I don't have the rootkit installed, but it seems pretty straightforward.

Personally, I would never use any windowing system by choice that did *not* have network transparency. Non-local VMs and applications with specific hardware requirements or physical attachments are the biggest (as specific examples that I have used *today*). I use VNC heavily (including KVM-to-VNC for boot level interactions with systems) but that is no overall solution since it doesn't give you integrated desktops usually (copy-paste, breaking out each remote window into a local window, etc).

I'd certainly accept something like (I currently use it) NX (No-Machine's X) when run in rootless mode. That works decently well for allowing remote GUIs to behave more or less like they were local.

md raid. The bug was in commit md/raid0: fix bug with chunksize not a power of 2 causing, you guessed it, a bug with a chunksize not a power of two. I guess "fix" was a bit diversionary.

The real problem was a macro modifying arguments that were later expected to be the unmodified version.

Marry this to Citibank's virtual credit card numbers (or similar offerings from other companies) and now you can use one-time credit card numbers for all transactions, bonus points if you can punch in a dollar amount too like citibank offers. Who *cares* if you card # is skimmed or not. At most one person will get the amount of money you wanted to pay. Otherwise, I would stay far away from the service.

A small but confusing typo on the period of the last average. Further research shows that http://www.eia.doe.gov/ask/electricity_faqs.asp defines the yearly average as: 11040 kWh, an average of 920 kilowatt-hours (kWh) per month. Which does translate into approximately 30kWh per day.

Sounds cool, but I think there are some practical downsides to living underwater.  UPS/Fedex deliveries.  Service calls.  Public utilities (fresh water, sewer, electrical, gas).  General safety in the face of disasters becomes much more of a concern.

Water cooling your servers might be easier--as long as the saltwater doesn't corrode your fittings.

Best leave this to plant growth labs instead of primary living quarters.

This is an xorg.conf which supports four screen display, two per
PCI card.  Note that not all X11 drivers support non-xinerama
mode (certainly with one card, possibly even with multiple
cards).  Specifcally the Intel driver people explicitly removed
the working functionality and refuse to believe that anyone
actually wants this

Section "ServerLayout"
    Identifier     "Default"
    Screen      0  "Screen Samsung NV1 CRT"
    Screen      1  "Screen Samsung NV1 DVI" RightOf "Screen Samsung NV1 CRT"
    Screen      2  "Screen Samsung NV2 CRT" RightOf "Screen Samsung NV1 DVI"
    Screen      3  "Screen Samsung NV2 DVI" RightOf "Screen Samsung NV2 CRT"
    InputDevice    "Mouse-MX510" "CorePointer"
    InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "InputDevice"
    Identifier  "Keyboard1"
    Driver      "kbd"
    Option        "XkbModel" "pc104"
    Option        "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier  "Mouse-basic"
    Driver      "mouse"
    Option        "Protcol" "IMPS/2"
    Option        "Device" "/dev/input/mice"
    Option        "ZAxisMapping" "4 5 6 7"
    Option        "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
    Identifier  "Mouse-MX510"
    Driver      "evdev"
    Option        "Device" "/dev/input/event3"
    Option        "Buttons" "10"
    Option        "ZAxisMapping" "9 10"
    Option        "Name" "Logitech USB-PS/2 Optical Mouse"
    Option        "Resolution" "800"
    Option        "Emulate3Buttons" "no"
EndSection

Section "Monitor"
    Identifier   "Samsung204LCD"
    VendorName   "Samsung"
    ModelName    "SyncMaster 204T"
    HorizSync    30.0 - 75.0
    VertRefresh  60.0 - 60.0
    DisplaySize 411 311
    Option        "dpms"
EndSection

Section "Monitor"
    Identifier   "Samsung226LCD"
    VendorName   "Samsung"
    ModelName    "SyncMaster 226BW"
    HorizSync    30.0 - 75.0
    VertRefresh  60.0 - 60.0
    Option        "dpms"
EndSection

Section "Device"
    Identifier    "nvidia1-crt"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName    "NV44A [GeForce 6200]"
    VideoRam    262144
    BusID        "PCI:3:1:0"
    screen        0
    Option "DPMS" "true"
    Option "RandRRotation" "true"
EndSection

Section "Device"
    Identifier    "nvidia1-dfp"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName    "NV44A [GeForce 6200]"
    BusID        "PCI:3:1:0"
    screen        1
    Option "DPMS" "true"
    Option "RandRRotation" "true"
EndSection

Section "Device"
    Identifier    "nvidia2-crt"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName    "NV44A [GeForce 6200]"
    VideoRam    262144
    BusID        "PCI:3:2:0"
    screen        0
    Option "DPMS" "true"
    Option "RandRRotation" "true"
    Option "Rotate" "left"
EndSection

Section "Device"
    Identifier    "nvidia2-dfp"
    Driver        "nvidia"
    VendorName    "nVidia Corporation"
    BoardName    "NV44A [GeForce 6200]"
    BusID        "PCI:3:2:0"
    screen        1
    Option "DPMS" "true"
    Option "RandRRotation" "true"
EndSection

Section "Screen"
    Identifier "Screen Samsung NV1 CRT"
    Device     "nvidia1-crt"
    Monitor    "Samsung226LCD"
    DefaultDepth     24
    SubSection "Display"
        Modes "1680x1050"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen Samsung NV1 DVI"
    Device     "nvidia1-dfp"
    Monitor    "Samsung204LCD"
    DefaultDepth     24
    SubSection "Display"
        Modes "1600x1200"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen Samsung NV2 CRT"
    Device     "nvidia2-crt"
    Monitor    "Samsung204LCD"
    DefaultDepth     24
    SubSection "Display"
        Modes "1600x1200"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen Samsung NV2 DVI"
    Device     "nvidia2-dfp"
    Monitor    "Samsung204LCD"
    DefaultDepth     24
    SubSection "Display"
        Modes "1600x1200"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "DRI"
    Mode         0666
EndSection

I suppose that could be true...if you didn't spend five seconds looking it up. Phoenix to Los Angeles (by ground) is 372 miles. Utsjoki to Helsinki (Finland, by ground) is 795 miles. Your argument may be correct in general but in specific...

Grrrr. I didn't notice the lack of linking during preview.

Did you actually follow that link? It goes to a junk page.

Perhaps one of these tools will be more useful:

• http://code.google.com/p/ratproxy/
• http://developer.spikesource.com/wiki/index.php/Projects:phpsecaudit
• http://pixybox.seclab.tuwien.ac.at/pixy/

Did you actually follow that link? It goes to a junk page.

Perhaps one of these tools will be more useful:

• http://code.google.com/p/ratproxy/
• http://developer.spikesource.com/wiki/index.php/Projects:phpsecaudit
• http://pixybox.seclab.tuwien.ac.at/pixy/

I got one of these yesterday, but really, who has time to remember such long numbers. However, I know that it had a "D2" in it, so I figure anytime I see a number which contains this unique fingerprint, I'll assume it is my number. Fortunately, no-one has violated my rights by posting a number with "D2" in it as a comment to this article yet. You all are warned!