hacker.org

Was there not a challenge where the way of finding the solution was very similar to this one, that is, the answer can be found by writing down pairs of cipher text --> decrypted text (or the other way round, as it were)?
I can't recall right now which one it was, but I do think there was one.

I know of atleast one more challenge where the answer lies within the key (won't state it incase it spoils the challenge). This one was slightly different in the sense that you could derive two different keys depending on how you write it down.

Mapping the ciphertext onto the plaintext (decryption key):

CIPHERTEXT: ABCDEFGHIJKLMNOPQRSTUVWXYZ
PLAINTEXT: XVIZLGPANSWEROJTCMDYUKBFHQ

More specifically, the word "ANSWER" appears. This is, however, an incorrect solution to this challenge. On the other hand, if we map the plaintext onto the ciphertext (encryption ket):

PLAINTEXT: ABCDEFGHIJKLMNOPQRSTUVWXYZ
CIPHERTEXT: HWQSLXFYCOVERINGZMJPUBKATD

We spot "COVERING" which gives us our answer and thus concluding the challenge.

laz0r wrote:I know of atleast one more challenge where the answer lies within the key (won't state it incase it spoils the challenge).

I found it now. Guess who it's from.

It seems to me that adum accepts slight variations on challenges, as this is what has happened here. So maybe I should do a substitution cipher challenge where the solution lies in the key, do a slight modification to it, and submit it. After all, if it has been accepted two times, third time's the charm!

AMindForeverVoyaging wrote:

laz0r wrote:I know of atleast one more challenge where the answer lies within the key (won't state it incase it spoils the challenge).

I found it now. Guess who it's from.

It seems to me that adum accepts slight variations on challenges, as this is what has happened here. So maybe I should do a substitution cipher challenge where the solution lies in the key, do a slight modification to it, and submit it. After all, if it has been accepted two times, third time's the charm!

There was no intention to copy another challenge. It simply posed as a warm-up for the following cipher, and I had plans to bring out a third.

This one took waaaayy too long. I probably looked at the string 'ANSWER' for hours and couldn't find the final step. That last one is a bit random, for my taste.