11-19-2017, 02:36 AM
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.
Regardless, hashcat does not support attacking this header.
~