2.) Mere access to a security company's internal network isn't as useful as it would be for, example, a credit card processor's internal network. (Except for stealing secret keys, etc) The more serious threat is not intrusion, but tampering. (Pretending to be a employee for sneaky NSA-style RNG-weakening, etc) Covert tampering is a heck of a lot harder.
It wouldn't take much for someone to sort out my HN profile regardless of my disclaimer though. My HN username is the same as my GitHub username, which is linked to the Silent Circle organization.
[1] http://arstechnica.com/business/2012/03/hacker-commandeers-g...
I'm on GitHub because we release the sources of our clients and because we use several open source libraries in our stack and it's very impractical to push changes upstream if you don't have a GitHub account.
I could certainly do that anonymously, but again... tradeoffs. It's more convenient for me to do it from my primary account (which makes me more likely to do it) and there are advantages to publicly sharing that we give back to projects that we use.
Do you think someone doing a recon on a target like a developer at Silent Circle _wouldn't_ check for a GitHub profile?
EDIT: Dunno who is downvoting you. You raise very valid points (ones that we have had many conversations about), and have been very cordial...
The more someone knows about you the more they could either find a way through you into the company, and eventually on to the servers.
Like for instance you might reveal something in your posts that could be used to find out more about you online and eventually get access to your amazon account, or paypal account, or your gmail account and use this to get access to your work email or enough information to impersonate you or impersonate someone who pretends to know you, until eventually they get in and find access to things Silent Circle doesn't want people to access.
Relevant: http://xkcd.com/538/