-----BEGIN PGP PUBLIC KEY BLOCK-----
xjMEYSVIzxYJKwYBBAHaRw8BAQdA3p7s7oz8X2OwHATFKWShQjLexcaBWyGM mHq5ok1npy3NNW9yaWdpbmFsMTdAcHJvdG9ubWFpbC5jb20gPG9yaWdpbmFs MTdAcHJvdG9ubWFpbC5jb20+wo8EEBYKACAFAmElSM8GCwkHCAMCBBUICgIE FgIBAAIZAQIbAwIeAQAhCRDrGND1ys+qQxYhBE0TIiXzefF0KP6ddesY0PXK z6pDMqcBAJnyeAkqLkVtE2xer2x9Wg48rQntO9HdrYFuFy9MCpeZAQCHBYEX hWJR0K9PkatNV+4m+ZZ/2Zyw7jsQdL8Ze84xAc44BGElSM8SCisGAQQBl1UB BQEBB0BZd4GGFk1whTWyY60+CyvHQITb43Rw3nfDdmgVJaC+DgMBCAfCeAQY FggACQUCYSVIzwIbDAAhCRDrGND1ys+qQxYhBE0TIiXzefF0KP6ddesY0PXK z6pDUyEA/RPdRQaylsyL81JCB0ZdPnwuhSVmtEHQK3e/OAwQuZDzAQDqanbp ii6GYCEodsnjiLP6x0+mCupghml+3kXOX4HmDA== =efCK -----END PGP PUBLIC KEY BLOCK-----
It would make me laugh to the heavens if he actually released some earth shattering Soros destroying big dick energy onto the universe after all the people call him a LARPer. I doubt it will happen, but I would be highly entertained if it happened.
Base64decode result reveals an email address 🤔
interdasting. Thought it would say ligma in binary, or something of the sort. Keep digging, but don't be too hopeful on this end. Take care, fren.
Tis the nature of public keys. I found the same when i imported to my gpg keyring. What strikes me is the invalid armor header. It's too long to be a bzzaddr. What does it mean?! It must of been inserted after the user exported the armored key.
amnesia@amnesia:~$ gpg --import ./original.mcafeepubkey
gpg: invalid armor header: xjMEYSVIzxYJKwYBBAHaRw8BAQdA3p7s7oz8X2OwHATFKWShQjLexcaBWyGM\n
gpg: key 0xEB18D0F5CACFAA43: public key "[email protected] [email protected]" imported
gpg: Total number processed: 1
gpg: imported: 1
I was gonna guess that that was the code. Almost had it cracked.
resume the hunt!
First Q then McAfee, I read that crap from telegram feed , all a bunch of fucking nonsense meaningless shit