I almost immediately marked it as spam, but I gave it a second thought. These were the e-mail headers.pic.twitter.com/MoZ9psNQQT
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
But now I have their key, in ASCII armored format, and it starts like this. Yes, they were using a non-commercial freeware version of PGP Desktop for commercial purposes. Version 9.10.0 has a code exec CVE from 2010. https://nvd.nist.gov/vuln/detail/CVE-2010-3397/ …pic.twitter.com/ghfwxEHBjN
So let's recap: 5 year old webmail, 6 year old e-mail server, >2 year old PGP with an arbitrary code exec CVE. The key itself? The userid was "CCN-CERT.PublicKey <CCN-CERT.PublicKey.Depart@CCN.es>", which does not match the sender of the e-mail either.
Not that this was going to go anywhere by now, but I replied with inline PGP, and sent them my phone number to see what their story was. I didn't hear back for two weeks. Apparently they had gone on vacation.
At least they managed to sign their message when they finally replied? Still using attachments though. I figured this wasn't worth wasting any more of my time on by then, didn't reply and never heard back.
So there you go, that was my recruiting experience from a branch of Spain's NSA. Not exactly a shining example of competence.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.