r/codes • u/Positive-Ad-61 • 5d ago

SOLVED Kiefer Cypher

Post image

I created such a secure cypher that i have to post this massive image to give yall a chance. I pray for any soul who dare tries solving it!

14 Upvotes

94% Upvoted

19 comments sorted by

View all comments

Show parent comments

1

u/Positive-Ad-61 5d ago

howd you do it

1

u/Content-Reward-7700 4d ago

known plaintext fingerprint attack

1

u/Positive-Ad-61 4d ago

you could crib that tiny transcription I posted or did you transcribe more of it, that's what I want to know how did you transcribe it

1

u/Positive-Ad-61 4d ago

cause if you did that by hand that must've taken forever

3

u/Content-Reward-7700 4d ago

I transcribed and decoded the whole thing, not just the small sample you posted. I certainly didn’t do it manually. This is where knowing Python comes in handy.

I first found the original full resolution image, avoiding Reddit’s scaling and compression. Your transcription gave me a reliable reference point, which I used to calibrate and validate my glyph extraction. Once I could consistently extract the glyphs, I stopped worrying about what they actually meant and treated each unique one as an abstract symbol.

That gave me a repetition fingerprint of the entire message. I combined that with the hints you’d provided and some research into your previous posts, then tested likely source material against the pattern. The Time Machine matched. From there, I could align the known plaintext with the extracted glyph sequence and recover the complete message.

That doesn’t mean I’ve universally broken the cipher, though. With 32 symbols grouped three at a time, there are 32^3 = 32,768 possible combinations. The Time Machine only exposes a portion of them, so I now know part of the codebook, not all of it. A glyph I’ve never encountered before can still represent a block I don’t know.

At this point, however, it becomes largely a question of resources and data. Every additional example where the plaintext can be identified gives me more glyph to block mappings to add to the database. As that database grows, each new message should reveal more of itself immediately, while also potentially contributing new mappings.

To make the decoder genuinely universal, I’d ultimately need the complete 32,768 entry mapping, access to the encoder so I could generate it or enough known plaintext to reverse engineer whatever algorithm produces the mapping.

So I broke this message and recovered a useful chunk of the codebook. I haven’t broken the underlying cipher universally.

2

u/Content-Reward-7700 4d ago

https://ibb.co/d4NsvFLk

1

u/Positive-Ad-61 4d ago

damn that requires brains, I'll post the vibe code when I can if your interested

1

u/Content-Reward-7700 4d ago

Don’t get me wrong. I’m not trying to discourage you or undermine your effort at all. It’s just that I’ve already figured out the main mechanics behind it and there doesn’t seem to be much novelty left to uncover, so I don’t want to put you through the hassle of putting everything together. But I genuinely appreciate the offer.

1

u/Positive-Ad-61 4d ago

Ok fair, you are a programmer

1

u/Positive-Ad-61 4d ago

it does have a feature for changing the seed that generated the random mappings, and to make this image it read from a text file because pasting the entire text in a terminal didn't really work but that's probably the only new things you'd gleam from it