Cookie is being included in POST (Using requests and preserving session, so it is auto-resent)
hash is correct
Still getting “Too Slow”. Not sure what I am missing. Any hints/help would be much appreciated.
Im in the same boat. Went so far as to get a VPS in london to get closer to the source and still no luck. I’d like a sanity check that its still possible.
I tried to do it with a bash script but It’s just not happening, takes about 150ms to finish, is curl just too slow? Would love if somebody who completed it with a bash script could take a look at my script or share theirs.
For those of you who are referring to speed. Making the script run faster is not the solution. Im not terribly good with bash so I’ll use python as an example. Whenever you make a request it is a completely new connection for every request. The trick is to send 1 request only. good thing to look into.
requests.sessions() ← golden goose
This is driving me crazy, my bash script wasn’t working so I wrote a python solution. Using requests.session() as you said, hashlib and beautiful soup (a million times easier than my regex solution) and it also doesn’t work. So I slapped it on a VPS to look if my internet is the problem, still doesn’t work. So I looked for a writeup and copied the guy’s code to my vps and even that still says too slow, even though the script apparently worked for the dude who wrote the writeup. So I’m pretty sure both of my scripts should work and the script from the write up as well, none of them get me the flag and I have no idea what the problem could be.
I am in the same boat. Used hashlib, Beautiful Soup, requests.session() for both get() and post(). Used tcpdump to verify the headers, cookies etc for both get() and post().
I’m in the same situation. I have done two scripts, one python script and one bash scripts. I’ve used wireshark to verify communication between server and client, cookies, headers times, etc… md5 hash is correct too. I don’t know what to think about it… some help?
@letMel00kDeepr said:
For those of you who are referring to speed. Making the script run faster is not the solution. Im not terribly good with bash so I’ll use python as an example. Whenever you make a request it is a completely new connection for every request. The trick is to send 1 request only. good thing to look into.
requests.sessions() ← golden goose
I can’t imagine just one request. One request is required to obtain the string and another request to send the string hash. right?? Do you mean one request? or one session ?
Today i re-ran my python script and got the flag in my response. I made no changes from the one that was failing 2 weeks ago. Seems like the challenge has been fixed.
Struggling with this atm, got the string extracted encoded and encrypted, posted into the text field and submit button pressed with Selenium but still says ‘too slow’. I’m assuming it has something to do with the cookies based off everyones comments but i’m not sure what exactly I can do with them?
Hi - In case anyone is interested on solving this challenge without scripting, I managed to get the flag using Burp. I am very happy with what I learned, it involved: Intruder, some grepping (part of Intruder options) and payload processing.
Got a single line bash script to do it all but with creating two sessions fastest it will go is 0.435s. So not so much how many ways but ‘can do you this in python’ really. Running the script in an EC2 instance got execution time to 0.169s but still getting back “too slow.”