Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hack your way through Stripe's Capture the Flag

stripe.com

Post reply on HN
Print view View original

81–90 of 219 posts

Re: Hack your way through Stripe's Capture the Flag

#81

Post by awm »

jcr wrote: post #79

You should note that the SSH key has been changed. $ dsocks.sh ssh level01@ctf.stri.pe @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a hos…

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

#82

Post by mjijackson »

jcr wrote: post #79

You should note that the SSH key has been changed. $ dsocks.sh ssh level01@ctf.stri.pe @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a hos…

Can anyone from Stripe confirm that this box is not rooted?

Re: Hack your way through Stripe's Capture the Flag

#83

Post by ab »

jcr wrote: post #79

You should note that the SSH key has been changed. $ dsocks.sh ssh level01@ctf.stri.pe @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a hos…

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

#84

Post by gdb »

mjijackson wrote: post #82
jcr wrote: post #79

You should note that the SSH key has been changed. $ dsocks.sh ssh level01@ctf.stri.pe @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a hos…

Can anyone from Stripe confirm that this box is not rooted?

Confirmed.

Re: Hack your way through Stripe's Capture the Flag

#86

Post by derwildemomo »

mirkules wrote: post #59
starnix17 wrote: post #54

Anyone having trouble connecting to this?

I was in there 5 minutes ago, did cat /levels/level02.c and then it stopped responding. I don't think cat could crash the server, but if it did, I'm sorry?

pretty sure it wasn't you. but then again, you never know with cats.

Re: Hack your way through Stripe's Capture the Flag

#87

Post by gdb »

awm wrote: post #81
jcr wrote: post #79

You should note that the SSH key has been changed. $ dsocks.sh ssh level01@ctf.stri.pe @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a hos…

Got that also, then keep getting: ssh_exchange_identification: Connection closed by remote host Looks fun too!

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

#90

Post by gdb »

heywire wrote: post #69
gdb wrote: post #49

Earlier quoted context omitted.

Yep, it's completely isolated. Someone rooting the machine is very much within our threat model :).

Must be fun watching all of the attempts... Do you have any way to monitor progress?

We don't have an exposed way. We'll probably do a summary blog post in the future with stats though!
Post reply on HN