danger/u/
This thread is permanently archived
Can you break the code?

| i found this -°°


uhajL8fX0TjzFD8tcabeK/vVnue4uzubuhajL8fX0ThHX3LFcu/BqNIG1rCA5Yn1yEtpsT98z2nn
M2AY39H2iIy/qGwyvSFrZhVcRGSNJGKsQbCc42ezBmbvFg3vtsZnUheesNgOMh1prnN/7iQCKLoW
oy/H19E4mEAcaqXQIpdnFr2CcYI+DLoWoy/H19E4LttuUuJotHtArzlTY/kjOfZV98kB4M7iILcZ
PJCeaik=


| Looks like a Base64, but I don't think it's using the usual UTF-8 character set.

Trying out the Windows 1252 and ASCII 7 gives jumbled character.

I might investigate this later-ish.


| Just a hunch here, this could be a Base64 encoded image. Simply because, for the life of me, I can't figure out the charset used here.


| I wouldn't even know where to begin lol


| >>65155
You can pretty much tell it's a Base64 by how the letters and symbols are arranged. However, if you put it through a Base64 to ASCII decoder, it'll throw jumbled letters once decoded.

I hypothesised that it was an image, but I very highly doubt that was the case. It simply lacks the length to be an image.

My second theory was for it to be a malformed URL transcibed to a Base64, but this is still not the case either...


| My final theory is that this is simply a malformed or corrupted Base64, so anyone planning to decode it might need to reconstruct the whole thing.


| what if this g/u/rl just smashed the keyboard with her face and posted


| >>65256
I did consider that after several rounds of trying to decrypt it, yeah.


| >>65256
It doesn't look like Welsh to me.


| >>65260 just remember, there a blenty of fish in the sea


| reminds me of one old ass thread on sageru where someone posted CP and encoded it like this


| maybe its a phrase that passed through many encoders


| >>65454
That could be very well true, yes. I have been looking at it from several angle myself but that is definitely possible.

For one, it could have went through some kind of hashing or salting before it goes to Base64. This could explain why when I try to blast it and have it decoded to ASCII (or UTF-8 for that matter), it just fails miserably.


| >>65305
Ah, like my grandma used to say, but sadly not in the context of puzzle-solving.


| this is the key

nDZ7Zm33o2j144Oxy/6uTXILkOzci7Jokr6K6DUcDC0ivSQp3djXY37KXOS9T3jh77JWPHWWkD+ilXNPf+wYzRbpBU+z8ZaKER3laVoEgebm8rNVbEMHK/kOmriRr5WGO9zNMpwzqiMUdKnZVS3ShOy6ck1Z5bruIUcVC1DBUFUJ/UiQEOlsMKAMyw+06HMMFx88laQwKds070GLHFTSdyyafC6lV6sUDGlaF1GJ6v8ZnBuY0zR8/fCOozReZ7+U3VT87ksW6CX0eLKC2B+bwFoPSJusP6VJV3Mronfe8OXTZGZgp0GvrvOHQqnC+a5BvpHCoDvHCeDZjpQ02aZo+kqDLgC+AixIbC0PhoajfkVZ5fyXfP36JqaOyLGURkgI


| >>65578
Thank you for inspiring me to actually look up byte reversal.

I still have no clue how to decrypt this, but we'll get there somewhere.

Total number of posts: 16, last modified on: Sat Jan 1 00:00:00 1513185544

This thread is permanently archived