Slashdot Mirror

← Back to Stories (view on slashdot.org)

Patching Paranoia - How Fast Do You Patch?

Posted by Cliff on from the closing-the-holes dept.

selfassembled asks: "I work for an IT group in the Boston area called Thrive Networks. After the most recent exploit was revealed, my company scrambled to get our client's servers patched within 48 hours. This is extremely difficult because no customer wants to be interrupted by a reboot during business hours. Our staff worked after hours to get this patch installed ASAP. How fast do you (or your IT group) install patches for major exploits like this? What do you consider to be an acceptable turn around time for a vulnerability patch that may not even have an exploit yet? After Blaster and Welchia we decided it's better to be safe than sorry, and our customers seem to agree."

4 of 681 comments (clear)

  1. I wait until... by Bull999999 · · Score: 4, Funny

    I wait until I get feedbacks from sites such as The Register to make sure that the patch doesn't break anything.

    --
    1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
    1. Re:I wait until... by croddy · · Score: 4, Funny
      I guess you didn't hear about the patch for XP that disabled Internet access for hundreds of thousands of users.

      well they should have POSTED about it! jeez!

    2. Re:I wait until... by hoggoth · · Score: 4, Funny

      > We used to have Groupwise, and pretty much every MS patch broke Groupwise

      I think "Breaking Groupwise" is an MS patch all by itself.
      "CRITICAL UPDATE: SOME SYSTEMS HAVE GROUPWISE INSTALLED ON THEM. THIS PATCH WILL BREAK GROUPWISE."

      --
      - For the complete works of Shakespeare: cat /dev/random (may take some time)
  2. Lie about it. by EvilJohn · · Score: 4, Funny

    If it's windows patch early, and patch often. If anyone asks why you rebooted a box, lie about it and say "It crashed." That's one everyone will believe.

    --

    Less Talk, More Beer.