Take the 2-minute tour ×
Information Security Stack Exchange is a question and answer site for Information security professionals. It's 100% free, no registration required.


ciphertext: TXOtWjYhVk 8&O$4AmSA

plaintext: http

ciphertext: cZf.

plaintext: http

ciphertext: r5Hz

  • This is definitely somehow decodable from ciphertext.

  • The ciphertext is always the same length as the plaintext.

  • Frequency of letters in the ciphertext doesn't match the plaintext.

  • The available charset seems to be upper and lower case alpha, plus .&-,%!$ and maybe others among the printable characters of utf-8.

share|improve this question

closed as off topic by Rook, TildalWave, Terry Chia, Adnan, Hendrik Brummermann May 19 '13 at 14:50

Questions on Information Security Stack Exchange are expected to relate to Information security within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

For all we know, it could be a one-time pad. A good cipher should produce output indistinguishable from random data, so if it's something good, we don't have any way of telling what this is. The only real clue you gave is the default output format that it uses (or I guess that's what it's formatted in) and that input and output are the same length (which still can be almost anything). –  Luc May 19 '13 at 1:17
what other useful info could i figure out to help discover what it is? –  princessbubblebutt May 19 '13 at 1:50
It could be one of these with an extended charset. –  Manishearth May 19 '13 at 2:32
Also, you have given two different outputs for the same http input –  Manishearth May 19 '13 at 2:33
@Manishearth - I could be Vigenère cipher, but then a number of distinct shifted alphabets (supporting key length also of such length) would have to be equal or greater than 28, otherwise it would still produce a distinct repetition. For example, taking the Wikipedia example for a spin, the plaintext ATTACKATDAWN and ciphertext LXFOPVEFRNHR would result in letter shifts of 11,4,-14,14,13,11,4,-14,14,13,-15,4 in UTF-8 character space, clearly indicating key length of 5 (Wiki used a key LEMON in the example) and letter space of 26 (shift of first and first before last character). –  TildalWave May 21 '13 at 13:55

1 Answer 1

This could be encrypted with any key length that is equal or longer than 28 characters (sum of lengths of ciphertext you provided) and as such unsolvable. The character variation between the plaintext CANDY VERY CRANBERRYhttphttp and its ciphertext TXOtWjYhVk 8&O$4AmSAcZf.r5Hz is:


or visually in a scatter plot:

               Scatter plot

I don't see any pattern in it. The encryption is obviously not a simple letter substitution, otherwise same plaintext characters would translate into same ciphertext characters. The function could still be a simple modulo n + shift k though. For example, using n of 32 and k of -80, the key (or rather the first 28 characters of a key of unknown length) could be:


Or agQXNrSsTbPEL^NBLkQ8K6B6Z9LZ with 40 -80 respecitvely. Of course, there are countless values of n and k that produce 28 printable character strings, and we can't say for sure only printable characters are accepted for the key either, or indeed that this is the encryption method used. Scatter plot suggests good randomness, which doesn't exclude advanced encryption algorithms such as AES, but nether it does a running key cipher or, as @Luc mentiones in the comments, one-time pad where the key used is at least as big as plaintext.

Your question is thus - with the data you provided being insufficient to detect any patterns or repetition - unsolvable.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.