gallois wrote:
42
But what was the question?
Indeed, that’s the whole point of base64 etc (to convert binary into printable ascii chars) but I looked at the decoded binary and couldn’t see anything evident there.
Every piece of information I included in the original string is important. Including what doesn’t seem to be base64. I think I gave you too much now 
echo ‘#QBdg%HGILH&R9vch)NBTAt5.X3oWb\BxMbn5,GR0wTQ*0xuHBc=’ | base64 —decode —ignore-garbage | hexdump
0000000 1740 1c60 0b62 1f1d 726f 4113 0b4c 5f79
0000010 167a 1c6c 6e4c 467e 4c47 4313 6e4c 171c
There does seem to be a pattern but I have no idea what to do with the special chars.
Nothing 0×80 or higher, is probably significant.
Everything is significant.
In general, when you see a set of data that looks like garbage, but it is not, what could it be then?
zipfile? Wrong signature.
So when you see garbled up data flying through the aether the first thing that pops to mind is a zipfile? 
Not going to be a zipfile, or other compressed data, since everything (in the base64 decode) is below 0×80.
