My understanding is that all applications of CBC within cybersecurity are stateful- however, this doesn't mean that CBC is, by definition, stateful. Isn't CBC just a method of encryption/decryption? If you could lead me to a source that CBC by nature (rather than the applications of) is stateful I will delete this kata. I still maintain that it's useful to know how CBC works. No need to be harsh by calling it a scam! Lmk if you think of a way to do random testing with it.

I see, thanks for that information, I appreciate it. I just entered tech/security center so this is all good stuff to know. I'll fix this eventually, but I don't see how this is relevant as a design flaw- it's a simplification of how CBC works, and it's more of an introduction to the concept of CBC encryption. Thoughts?

Right, that's true. Do you have any suggestions for how I implement random tests?

(hopefully) made it much clearer now. Also, I did implement a series of random tests so that people cannot cheat anymore. Thank you for your input!

Fixed all of those things. Thank you for your input!

Added random tests/fixed suggestions, thank you for your help!

Thank you! Will work on it now.

Thanks for checking! When I wrote that, the text length I was referring to was the text length in binary.

Everything is coded in base64, so one character = 6 bits. If the text is 25 keys long, its 150 bits long. 150 is a multiple of the length of they key and IV.

I do understand that it's not clear, so I'm currently reworking my own code to make it so that it will encrypt any length of text as long as len(key) == len(iv)

Thanks for your comment!