Decrypting usenet headers, part 2
#2
I'm not familiar with that specific header, but - just speculating - it looks like a proprietary encoding/encryption scheme. When specific ecosystems (like Google) insert such public headers for their own private use, it's likely that part of the scheme includes a private component that only they know.

Regardless, hashcat does not support attacking this header.
~


Messages In This Thread
RE: Decrypting usenet headers, part 2 - by royce - 11-19-2017, 02:36 AM