Timeline for How do I move from RCE being a hobby to RCE being a profession?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:49 | history | edited | CommunityBot | replaced http://reverseengineering.stackexchange.com/ with https://reverseengineering.stackexchange.com/ | |
| Mar 16, 2017 at 15:51 | history | edited | CommunityBot | replaced http://meta.reverseengineering.stackexchange.com/ with https://reverseengineering.meta.stackexchange.com/ | |
| May 25, 2013 at 20:24 | vote | accept | Avery3R | ||
| Apr 17, 2013 at 11:06 | comment | added | joxeankoret | Eeeh... almost all people I know from 'some old celibrity virus groups' are working in this 'related field'. And their employers know this point very well. Indeed, they were contracted because of this fact. BTW, I used to work in that field. Perhaps what you say happens outside Europe, I don't know. | |
| Apr 17, 2013 at 6:24 | comment | added | 0xC0000022L♦ | @Ange: still I know of at least one case where this was knowingly done in the past. I know what the official stance is in most companies, but that doesn't always match up. And to my knowledge exploits, which includes PoC, aren't part of the taboo list either. | |
| Apr 17, 2013 at 6:11 | comment | added | Ange | the 'not hiring anyone who ever wrote a single malicious file' may still be true today (even in Europe). packers, debuggers, tutorials: OK. Rootkit, exploit, malware: forget it. Even if you're merely associated with anyone who wrote one, and you actually didn't. I can't talk for ALL companies of course, but that's the actual stance of some of them. | |
| Apr 17, 2013 at 1:19 | history | edited | 0xC0000022L♦ | CC BY-SA 3.0 | added whole section about anti-X industry specifics |
| Apr 16, 2013 at 23:33 | history | answered | 0xC0000022L♦ | CC BY-SA 3.0 |