gdb

33 ms·

1. 331.▲
   by gdb 15y ago

   Unfortunately, we won't be webcasting. We will be releasing official solutions at some point however.
2. 332.▲
   by gdb 15y ago

   We're taking a look! (Bleh, spinup scripts not working as well as you'd like....)
3. 333.▲
   by gdb 15y ago

   I think the machine was actually hosed due to fork bomb. (I kept bumping the rlimits as more people logged in and ran up against nprocs, but the last time I clearly just bumped nprocs way too high. Live and learn....) You certainly should b
4. 334.▲
   by gdb 15y ago

   We don't have an exposed way. We'll probably do a summary blog post in the future with stats though!
5. 335.▲
   by gdb 15y ago

   That's what happens when hundreds of people try to SSH into a machine at once :). (That error due to SSH's maxstartups being exceeded.)
6. 336.▲
   by gdb 15y ago

   Confirmed.
7. 337.▲
   by gdb 15y ago

   New host :). We brought up a new machine for this, and didn't copy over the SSH keys. Never hurts to be paranoid though.
8. 338.▲
   by gdb 15y ago

   Yeah, we're rebooting. Should be up in a few more minutes. Sorry about that.
9. 339.▲
   by gdb 15y ago

   Yep, it's completely isolated. Someone rooting the machine is very much within our threat model :).
10. 340.▲
    by gdb 15y ago

    Bumping rlimit! Should be good for now.
11. 341.▲
    Hack your way through Stripe's Capture the Flag(stripe.com)

    391 points by gdb 15y ago|198 comments
12. 342.▲
    Source-diving as a system administrator(blog.ksplice.com)

    66 points by gdb 16y ago|7 comments