Written down, because custom keybindings are nice
Kali has user defined print screen. Parrot doesn’t. Let’s fix that without using the internet.
When I first started using Linux, I googled prettymuch everything. These days I find that the fastest answer is probably already on the terminal. To this end, I frequently lean on
apropos; the french term for ‘pertaining to’.
In this situation it yielded exactly what I was looking for. A quick glance at the manpage shows the answer I was looking for in the invocation:
I navigate to the keyboard shortcuts screen through the gui, and drop in the invocation, and set the keys I want to use. EZPZ, and we’re done.
Very good. Apropos is all the body needs.
I did these one day for a hands on style demo on how to solve introductory CTF problems a few years back and thought I’d post them my CClub flaybies to have a fat gander at.
With these, as well as with my other writeups I often times mention things I tried, but didn’t succeed in, as well as some of the hints I acted upon rather than just following the straight line to the solution.
It’s a style choice to remind you that the answers are not always obvious, and that in most CTF’s you’re going to have to try a few things before you find the right track to get on.
This is a PDF because my old notes are in cherry tree and it was easier and I don’t even feel bad.
Be sure to get real nervous before deciding you don’t care and clicking it anyways.
A lot of us, as hobbyists only used Burp Suite when we were diving into a CTF. Since that sort of use is timeboxed and we’re generally in a mad scramble to grab flags, we tend to ignore quality of life changes and learning the deeper configuration options.
Perhaps the most common example I see my peers dealing with is trash from the Firefox ‘success.txt’ messages, slack ping-pongs, and the mass amounts of google nonsense and noise while you’re using intruder.
In a meek attempt to save your sanity while forwarding 30 requests for every proxied request you may have done something dumb like using the interface options for ‘proxy/intercept/action/don’t intercept requests to this whatever
When in truth, this actually just limits scope in your HTTP history.
This feature phenomenal on actual assessments when you need to verify reproducibility and provide veracity in your documentation rather than what you might get if you were aggressing through a CTF challenge to try and get the flag.
A more advanced method of wasting your time is in resorting to the target/scope functionality itself. You may be confused when this illusion fades and you still find your intruder queue mired with garbage from across the intersphere.
Inside of Proxy/Options/Intercept Client Requests is a custom rulebox w/ several default options. The singular checked rule ‘And URL Is in target scope’ is what you need (After you’ve specified the scope)
TLDR; DO THIS
This should spare you everthing except for websockets requests. Keep in mind that the default rule is a boolean ‘AND’, so you need to specify another rule first.
To deal with the websockets requests, drop to the line below and unselect the websockets selections.
Now you’ll be free to use Firefox both for your attack, and your CTF chat, or just updating your garbage blog instead of hacking boxes.