Actually it is a valid Base64 string - it just decodes to 24, 106, 27, 67, 102, 236, 169, 222, 184, 61, 117, 64, 153, 160, 226, 12, 24. To get [email protected]<mailto:[email protected]> you would have to XOR that resulting binary string with 124, 31, 118, 46, 31, 172, 108, 174, 217, 80, 5, 44, 124, 142, 129, 99, 117 which I don't see any pattern in (close to that anyway, I did it in my head so I'm sure I screwed up some of them). Maybe someone sees something... Of course, Cal could have done it, which means it's probably Matrix for "titties." :-p
The input and output are both 17 bytes, so an XOR makes sense, but another 17 character example would help. And a 20. t From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, April 07, 2011 1:23 AM To: [email protected] Subject: [Full-disclosure] Cipher detection Hi Full-Disclosure, I'm trying to figure out what kind of cipher was used in this: GGobQ2bsqd64PXVAmaDiDBg= Looks like Base64, but it's not. The original string is: [email protected]<mailto:[email protected]> Thanks all! wbr, - Max
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
