New encoding security!
It's the C GOD coming back at you again!
I took my knowledge on bmp image rendering and used it to my advantage.
Disclaimer: What you see in this example is just with no offset. I am going to be adding in support for reading the image that has an offset.
What is this new type of encoding security?
So, I made it to where you can render a string into an image.
Yes. You read that right. You can now encode a string into an image, and no one will ever know what that image says.
But, however, I did create a function that decodes that image and displays what that image is secretly hiding from you, just in case you forgot!
As of right now, there is just support for a image with no offset. I did, however, add support for having a offset to the pixel array of the image, which will then be need to be embedded within the decoding part. But, I was simply too lazy to get to that tonight.
What is an offset?
A image with an offset is just a image shifted to the right by 1, 2, 4 or 8 bits. This was just something I had added for the fun of it.
Why did I add this feature?
I figured I'd play around with the pixels a bit and see how creative I could get with them. And, the idea of a pixel offset was just the right idea.
It takes the current pixel, matches it to the pixel 1, 2, 4 or 8 bits ahead of it, and then copies itself to that pixel.
This basically "shifts" the colors to the right
So, just take a look at
0.bmp, it is quite a interesting image, take a guess at what it is that the image is secretly hiding from you, then run the code to see what it really says!
Tell me what you think! And please don't hesitate to tell me what to add!
So, just take a look at 0.bmp, it is quite a interesting image, take a guess at what it is that the image is secretly hiding from you, then run the code to see what it really says!
Bruh, the repl is private???