I'm working on an old CTF challenge where AES-128 was used on a 16 byte block. I have the round 10 key and the ciphertext. What techniques exist for obtaining the plaintext?
I think we should treat those questions just like any other question.
There are multiple reasons for that:
Most such questions tend to be rather poor anyways and can then be easily closed under the "analyze ciphertext" reason.
There isn't that many things you can do with cryptography and CTFs ...
I mean as long as it's well written and on-topic, what's the issue?
+4 (I added my vote since I agree with it). And at least it's pointing towards a consensus. Meta doesn't really create rules that are written into stone. It's more of a declaration of intent from users and is used to set precedent for future concerns.
The problem with treating it as a homework question is that it doesn't help people who want to know the answer. I mean, if I wanted to know the answer but OP was only given a hint, what would I do? Create a new exact duplicate and hope it doesn't get closed rightfully as an exact duplicate?
If someone doesn't want the answer, they wouldn't be asking here.
I accidentally created and added info for the "hash-based-cryptography" tag, which I didn't know there had already been a "hash-signature" tag.
I suppose they should be merged, given there's unlikely a public-key encryption or key encapsulation scheme based on cryptographic hash functions.
It seems like every once in a while there is someone asking about encrypting small messages. I wonder why. Are all these people working on systems with extremely limited bandwidth? Is it some problem that students commonly try to solve?
I'm working on an old CTF challenge where AES-128 was used on a 16 byte block. I have the round 10 key and the ciphertext. What techniques exist for obtaining the plaintext?
I think we should treat those questions just like any other question.
There are multiple reasons for that:
Most such questions tend to be rather poor anyways and can then be easily closed under the "analyze ciphertext" reason.
There isn't that many things you can do with cryptography and CTFs ...
I accidentally created and added info for the "hash-based-cryptography" tag, which I didn't know there had already been a "hash-signature" tag.
I suppose they should be merged, given there's unlikely a public-key encryption or key encapsulation scheme based on cryptographic hash functions.
