4 ms·
This - with some extras 0. Choose three things in Dev you are good at and make them your calling card. Loved automating sysadmin - puppet, ansible and salt sh
by lifeisstillgood 12y ago
This - with some extras
0. Choose three things in Dev you are good at and make them your calling card. Loved automating sysadmin - puppet, ansible and salt should be all over your blog.
1. LinkedIn is great, take sometime this evening to update your profile, focusing on the three calling cards. Everyone you take for coffee will look you up - a LinkedIn profile without a photo and upto date data is like not wearing a suit at an interview. It might be ok but most people just expect it.
2. Don't hide your past - don't ever ever lie about it - that will wrap you up in guilt and fear and shoot your sanity to pieces.
3. You seem to feel you have a justification for the actions you took - see a lawyer, take reasonable steps to have your side of the story into court (counter suing your employer?).
Someday your past will be used against you for political reasons - it will be very helpful to say "I am still in process of counter suing and the case is with the Florida blah" as opposed to "but I was innocent"
5. Taking people to coffee is great - taking them to coffee to discuss their experiences with your calling card areas is even better cos it has a higher hit rate and the "got any jobs going?" part comes much later
6. Never ever lie about your past. Ever
7. See 6. No matter how tempted.
- tptacek 12y agoThis is good advice, I think, but without getting into a lot of details, (3) is probably not going to be useful to Scott. If it were me (it isn't, so again, grain of salt), gentle contrition and hard-earned wisdom would be the narrative I'd apply. He's got nothing to beat himself up over, but the message he probably wants to send to employers is "that sucked, not ever doing that again".
- lifeisstillgood 12y agoHmm I may have misunderstood - I thought he was working for the vulnerable site as opposed to reporting it publicly (and presumably disclosing how he found out) I am overly cautious on public records that are not obviously favourable to oneself - certainly have an attitude of juvenile regret, but I would be tempted to look at this area closely. But it is certainly a long term thing and will not help getting a job now.
- tptacek 12y agoWhat seems to have happened in this case is that Arciszewski stumbled unawares into what is in fact a cut-and-dried CFAA violation. Contrary to extraordinarily widespread and dangerous popular belief, it is not lawful to test random sites on the Internet for security flaws. It is unlikely to ever be lawful to actively exploit flaws on sites without permission. Arciszewski POC'd a serious vulnerability on a site, and had the misfortune and poor judgement to do so during the middle of a huge law enforcement shitstorm. If that happens to you, I think the impression you don't want to create is that you vigorously contest the criminality of your actions. That impression comes freighted with the concern that you might think exploiting vulnerabilities without permission in order to make a point on Twitter is a good idea. That concern is, to many employers, both valid and relevant. Instead, I think you want to create the impression that you've learned that the standards are strict for not messing with other people's systems without permission. And that you've learned better than most other professionals that systems in production are not to be trifled with out of process. And thus that of all the people a firm could hire, you're among the least likely to cause outages and disruption by making dumb out-of-process changes. For whatever it's worth: if you want Exhibit A for why I don't have a lot of sympathy for people involved in "Lulzsec": breaking into sites and circulating credit card numbers and dumping databases created a set of circumstances that law enforcement absolutely had to respond to, and that's what sets up the crossfire that undisciplined but well-intentioned bug hunters get caught in. The people who go beyond doc'ing vulnerabilities to dump databases and take down sites are in some sense ruining things for everyone else.
- jcampbell1 12y agoYour description of the events seems overly mild to me. I read that he POC'd a site, and then disclosed it the same day to @lulzsec. The latter is what got him the felony, but you make it seem like the former or his timing was the problem.
- sarciszewski 12y agoThe FBI agents said if I had done it six weeks prior, they wouldn't be arresting me they'd be saying "Don't do it again."