3 ms·
> Do you think he....didn't know how to decrypt the PGP encrypted description? And that he was too embarrassed to say so? The first part is OK, he is a direct
by chx 9y ago
> Do you think he....didn't know how to decrypt the PGP encrypted description? And that he was too embarrassed to say so?
The first part is OK, he is a director, not a grunt. The second is harder to understand. He should've handed the entire thing over, starting with the PGP thing to an actual security knowing engineer.
- harryh 9y agoOr he could google it. I don't know how to PGP decrypt something off the top of my head, but I'm confident that 5 minutes of googling would lead me to any number of web pages to show me how.
- chx 9y agoThat's not an efficient use of his time. The first answer instead of that adversial crap should've been "Let me introduce you to my colleague John Doe who will be handling this matter. John, a mutual acquaintance introduced Dylan to me as a reputable security researcher, please handle his report. -Signature." He is a director, he needs to delegate ferociously. Unless it's organizing, strategizing etc it's below his concern. I have been on the receiving end of such emails a bazillion times in my carrier. My boss or the boss of my boss is certainly not going to bother with such small affairs. It is my duty to inform him when it turns out to be a big affair then he can begin to coordinate with engineering, marketing and so on to do the release. That's his job.
- wglb 9y agoBut he didn't do any of this. If you are CSO or CISO or director, you dang well better know what gpg is, and how to quickly find someone in the organization who knows how to deal with it.
- AstralStorm 9y agoThe whole problem is that there has to be a competent engineer who does not want to use this knowledge to get famous. See, a Security Director would love to see a direct report of their inadequacy buried... if someone knows then it is harder to bury.