News for hackers. Stuff that matters.
Re:IPv6 Attack Kills Mac OS X and makes Windows Server 2012 ... by rwg on Wednesday December 12, 2012 @01:33AM (#4908940)
I've never thought to put CVE-IDs I'm credited for reporting on my resume. Is that...a thing? Do tech employers (outside of security consultancies) even know what a CVE-ID is?
Re:IPv6 Attack Kills Mac OS X and makes Windows Server 2012 ... by ghshephard on Wednesday December 12, 2012 @03:54AM (#4909260)
What else should a person put on their resume (beyond job experience) when applying for security roles? Patents? Education? Open Source Projects? I would think that CVE-IDs would certainly lend color, and probably credibility to the resume of someone applying for a security position, particularly if the CVE-ID (which has some amount of peer review) was associated with something interesting or relevant to the position being applied for.
Re:IPv6 Attack Kills Mac OS X and makes Windows Server 2012 ... by splicer on Wednesday December 12, 2012 @01:50AM (#4908993)
It helped land me a firmware development position at what was then a fortune 500 company.
Re:IPv6 Attack Kills Mac OS X and makes Windows Server 2012 ... by bonzoesc on Wednesday December 12, 2012 @10:37AM (#4910534)
I'm at Basho (we make the Riak database) in a non-security role, and I pay attention to CVE-IDs. They'll stick with me and make me remember a resume better, and improve somebody's chances of advancing to an interview, and give me something to ask about during an interview.
Re:IPv6 Attack Kills Mac OS X and makes Windows Server 2012 ... by marshray on Wednesday December 12, 2012 @06:33PM (#4913143)
If your resume has them, the others don't, and the boss is knowledgeable or curious ... then it could help you stand out. I would think it would look very good for a developer position, especially at a place that makes high reliability and/or network facing products.