This is a rather interesting problem. One the one hand, it means git can compress this kind of content very well. On the other hand, this means any algorithm that can compress this well (like git) will eventually produce such decompression bomb.
I think Level 2 of this repo would be not having it nuke the memory and rather nuke the disk…
You could definitely do this! Just keep width ^ depth to a reasonable value and make blob_body large. Some code to make your own git bomb is here: https://github.com/Katee/git-bomb#readme
This is a rather interesting problem. One the one hand, it means git can compress this kind of content very well. On the other hand, this means any algorithm that can compress this well (like git) will eventually produce such decompression bomb.
I think Level 2 of this repo would be not having it nuke the memory and rather nuke the disk…
You could definitely do this! Just keep
width ^ depthto a reasonable value and makeblob_bodylarge. Some code to make your own git bomb is here: https://github.com/Katee/git-bomb#readme(Worth highlighting here that @kate is the author of this blog post.)