Unrelated: About a year in they sent me an award for continued contributions, but there's a puzzle on it I'm yet to solve; if anyone runs across this I'd appreciate any input!
Edit: The main page of above site has a lot more publications referenced. Worth a look.
EDIT: Other thing to note, is you can define, a set of operations, ex: https://gchq.github.io/CyberChef/#recipe=ROT13(true,true,13)
and get a shareable link
At first glance, only feature requests I might have added when I did this sort of work would be in for audio spectrographs in the multimedia section. Useful for finding stego, embedded thumbnails, hidden channels etc, and a generalized malicious ZIP parser that deals with the myriad of nasties packers can use.
The demand to scale this capability within an agency like that makes it worth while to build tools like this, wonder whatother easter eggs are in there beyond alert msgs.
Brits, so cheeky.
This is REALLY cool. Basically given an unknown string or file from something CTF-y you can run this tool on it to look for low-hanging fruit like it being e.g. base64 encoded.
(Binwalk is a fast, easy to use tool for analyzing, reverse engineering, and extracting firmware images)
While I appreciate that they made a web version I think they scattered their efforts to create different versions too much so that the project suffered regarding features and quality.
If the problem is that clicking is too cumbersome, then add better keyboard support. That's the solution to the problem as stated. You don't need to throw out the whole UI for that, and there's lots of things a GUI can do that a CLI can't.
I haven't been able to determine if this is the common reaction because people simply assume a GUI can't have good keyboard support, or because they're making an excuse for some unstated other reason.
And anyone who goes through the effort to learn all the custom keyboard shortcuts for your application is likely a person who would quickly pick up a standard CLI, so why not save them the effort?
And once you do end up learning all the keyboard commands for an application having clickable things on screen becomes redundant. So what do you end up with when you remove all that? Just some representations of inputs and outputs, which again can be clearly displayed in a CLI terminal in some format. And because inputs and outputs rarely need to take up the whole screen, just delete all the extra whitespace too so you end up with a very compact workspace.
But at that point, just reduce your program down to a CLI and keep it in its purest form.
I am glad this project has a decent Node API.
macOS seems to have eschewed good keyboard support for operating the GUI -- Steve Jobs insisted on a single button mouse because two buttons were two complicated; I could assume he would have disliked the idea of operating without point-and-click by only using the 100+ keys on a keyboard. I've witnessed many 'admins' in IT departments all to happy to point and click around their Windows AD admin interfaces without ever even thinking to ask if something faster is available.
My point here is that, anecdotally, the keyboard users and the mouse users apparently don't overlap much. This leads to keyboard users just wanting "CLI everywhere!" without consideration for a GUI with good keyboard support. I think you make an excellent point (that honestly didn't occur to me): If the problem is that clicking is too cumbersome, then add better keyboard support. It's an open source code base - we can certainly bring ourselves to bear on scratching this itch.
Web browsers are as GUI as they come, and arguably have far better scripting support than any CLI program.
It also reminds me of OpenRefine, another very cool online data processing tool with a slightly different focus.
"RFC 1149.5 specifies 4 as the standard IEEE-vetted random number."
so is any of the input feeding back to GCHQ?
I am wondering why people don't do the due diligence of searching if a tool/article has not already been posted before submitting a duplicate item.
I am sorry if you did interpret this as `trying to make fun of people` – This is not my intention.
I still would like to know why duplicate entries are welcomed/accepted on a news aggregator (honest question)!
I don't see anything wrong with reposting perennially useful stuff at reasonable intervals. Maybe twice in as many months is too much in general, but it seems to have worked out all right.
Putting such things in public code like that which would both directly point the finger at them and possibly turning secrets into widespread knowledge in the security community would be... incredibly stupid.