3 ms·
+1; getting their 500 page with some info that looks like it's base64 encoded, but it doesn't decode to anything useful running it through `echo -n '[...]' |bas
by seanp2k2 13y ago
+1; getting their 500 page with some info that looks like it's base64 encoded, but it doesn't decode to anything useful running it through `echo -n '[...]' |base64 -d` . Any ideas what format that is?
- VMG 13y agocould easily be encrypted data
- cdodd 13y agoIt's probably an encrypted stacktrace
- nwh 13y agoI'm going with everybody else, it's an encrypted stack trace. Every reload is entirely different rather than small portions changing, so we can assume it's something like AES rather than a simple XOR. If it were a simpler encoding we would see largely similar areas with just small sections changed for server IDs and timestamps. The distribution of the data is for all intents random, and it's too big to be an identifier on it's own, so that's the only logical explanation I can come up with.
- benmmurphy 13y agothe decoded data has a frequency distribution similar to random output so probably encrypted :) maybe that did something lolzy like stream cipher with the same key.
- kroo 13y agoIt looks like it's a url-safe base64 encoding of an encrypted blob (perhaps a stack trace). They're using '-', and '_' instead of '/' and '+'. Replace these characters and base64 will succeed, leaving with ~3k bytes randomly distributed between 0x00 and 0xFF.
- yeukhon 13y agoI am confused why they need to include that if there is little customer support.
- scott_karana 13y agoI believe it's a pre-Google legacy. I seem to remember seeing it a few times back in the day.
- yeukhon 13y agoInteresting. If this is the case, then there must be a good reason not to stop rendering that. I am also curious if each server has its own private key or not. Anyhow, thanks for the info.