Re:Hack your way through Stripe's Capture the Flag
by ab on Wednesday February 22, 2012 @06:52PM
(#3623094)
Not to worry, we spun up a new machine and didn't copy the ssh key from the old one.
2048 74:67:32:4a:04:b8:9f:05:b6:e8:29:43:26:12:75:11 /etc/ssh/ssh_host_rsa_key.pub is correct.
Re:Hack your way through Stripe's Capture the Flag
by mjijackson on Wednesday February 22, 2012 @06:50PM
(#3623085)
Can anyone from Stripe confirm that this box is not rooted?
Re:Hack your way through Stripe's Capture the Flag
by gdb on Wednesday February 22, 2012 @06:57PM
(#3623117)
Confirmed.
Re:Hack your way through Stripe's Capture the Flag
by awm on Wednesday February 22, 2012 @06:50PM
(#3623084)
Got that also, then keep getting:
ssh_exchange_identification: Connection closed by remote host
Looks fun too!
Re:Hack your way through Stripe's Capture the Flag
by gdb on Wednesday February 22, 2012 @07:03PM
(#3623151)
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.)
Re:Hack your way through Stripe's Capture the Flag
by jetsnoc on Wednesday February 22, 2012 @06:49PM
(#3623081)
I'm estimating they booted a few new EC2 systems up. Right before the system got a new key it was unavailable.
Re:Hack your way through Stripe's Capture the Flag
by lawnchair_larry on Thursday February 23, 2012 @01:34AM
(#3624039)
Rooting the box would not change the key.
EDIT: As confirmed by gdb and ab below, there's a good reason for the key change.