collisions VS jqp

That is still an attack on the second preimage or a collision resistance properties of the hash function. Most collisions do work this way, for example see [1].

[1] https://github.com/corkami/collisions

it's easy to do if you have a few hours to spare

remelem nem checksum ellenorzesre https://github.com/corkami/collisions !

Sure, here are two different screenshots of your comment made with this tool:

Hash collisions and exploitations – Instant MD5 collision\ (4 comments)

You may be familiar with some utilities that provide this interactivity, like jqp, but these come with their own downsides, namely subtle bugs due to the re-implementation of the original JQ in language X, but also they are additional dependencies you have to track and install for your platform architecture and OS/distribution.

Jqp: https://github.com/noahgorstein/jqp (for more complex jq stuff)

Also check out jqp (jq REPL) for when you need a few tries to get the right jq selector: https://github.com/noahgorstein/jqp

Looks a bit like fzf combined with jq.

jqp the Text User Interface for playing about with jq might help a bit.

You can have your input JSON terminal left, the output post jq terminal right and interactively edit your jq script elements above.

( based upon the Go implementation of jq )

See: https://github.com/noahgorstein/jqp

I also showed using a TUI wapper around `jq` called `jqp` https://github.com/noahgorstein/jqp which can be nice when iterating on a `jq` filter

Jqp – A TUI playground for exploring jq\ (22 comments)