News for hackers. Stuff that matters.
Re:Google CTF 2019 by kwesthaus on Saturday June 22, 2019 @09:41PM (#20252760)
Same. As far as I can tell, none of the usual restricted shell escape tricks work, so you just have to search through all the binaries on the system until you find one you can abuse to print the file contents, and that seems like more of a time sink than it's worth.
Re:Google CTF 2019 by grafporno on Saturday June 22, 2019 @11:28PM (#20253128)
env /bin/busybox strings README.flag
Re:Google CTF 2019 by scrollaway on Sunday June 23, 2019 @07:44AM (#20254864)
Nice one! Was wondering if there would be a way to call BusyBox with one of the missing binaries.
Re:Google CTF 2019 by shripadk on Saturday June 22, 2019 @09:45PM (#20252776)
Use iconv.
Re:Google CTF 2019 by archgoon on Saturday June 22, 2019 @09:53PM (#20252800)
LOL; I used split in the temp directory to create files of a single byte each and ran md5sum on them.

That's quite a bit more straightforward :)

Re:Google CTF 2019 by shripadk on Saturday June 22, 2019 @09:59PM (#20252820)
Well I spent an hour trying out as many commands as possible before giving up. Then came across this comment: https://news.ycombinator.com/item?id=20252612 and went through his Twitch recordings to see if he could get past this stage. That is how I learnt about iconv. :)
Re:Google CTF 2019 by redbluething on Saturday June 22, 2019 @11:31PM (#20253144)
Hehe. I kinda love this though :P
Re:Google CTF 2019 by RaptorJ on Saturday June 22, 2019 @11:20PM (#20253093)
shuf also works (its in /usr/bin) -- this took me a ~long~ time to figure out