Irc, cron, ldap, spying on other employees stuff
Yea, admins.
Figure out who's leaving the company: dump, diff, repeat
181–190 of 392 posts
Re: Figure out who's leaving the company: dump, diff, repeat
#182[deleted]
Re: Figure out who's leaving the company: dump, diff, repeat
#183Re: Figure out who's leaving the company: dump, diff, repeat
#184[flagged]
Re: Figure out who's leaving the company: dump, diff, repeat
#185I'm a WFH worker. My company is fully remote. They are really great at managing departures and make sure everyone's aware and has a chance to say goodbye.
However I can't shake this feeling that the mindset that got us from treating servers like pets to treating them like cattle is creeping into workforce planning, and the WFH movement is making it that much easier.
Why plan capacity when you can scale resources up and down on-demand on a whim? With the emotional and morale implications of letting people go hugely reduced it becomes easier to think like that.
Re: Figure out who's leaving the company: dump, diff, repeat
#186Earlier quoted context omitted.
Watching people’s accounts go into deactivated status in Slack with no goodbye is sad. The most toxic boss I ever worked for would request access to former employee’s Slack accounts under the guise of looking for data to transition their job. Their accounts would periodically go green when he logged in as them. Spooky to see ex-coworker accounts go green and know the boss is scouring their private messages. I know co…
Fortunately in Europe what the said boss did is illegal and this can end with a criminal prosecution.
The rules on this vary across Europe, though broadly speaking accessing an employees mailbox is “something you only do after speaking to legal”.
The patchwork of national laws and national interpretations of EU regulations is quite interesting, and rather confusing especially if you do offensive security work or DFIR.
As an example, when doing consultancy we would do the usual phishing as part of an assessment. Usually this is followed by dumping the users mailboxes to look for further credentials/access to corporate resources (eg: are they emailing passwords around?) - but in some countries such as Germany that’s often explicitly ruled out due to fear of breaching privacy regulations.
Re: Figure out who's leaving the company: dump, diff, repeat
#187Earlier quoted context omitted.
The lockout always struck me as dumb and I didn't do it as a manager. If I trusted them for the 3 years they worked for me, I can trust them for another week or two. Tie up loose ends, take your time. We're all adults here. I understand that under the worst circumstances bad things can happen but that's always the case.
I worked at a large web dev company and for years they had this attitude. Then one designer put in his two weeks and spent the majority of the time downloading all the site files for all of the sites the company had built over the two years he was there. We're talking hundreds of static sites where he took the all the design docs and static HTML/CSS/JS files one would need to recreate them somewhere else. Instead of…
So what stops people making their “backup of files” before hitting send on the email?
Re: Figure out who's leaving the company: dump, diff, repeat
#188LDAP's full of secrets. It's a great way to keep tabs on what's going on in a company. And to think that you can get nearly all of it with anonymous access. Team or department mergers before they were announced? Yep, I've caught those. Secret mailing lists for internal projects? Check who's a member and you can ferret out what's going on. Bonus if the list mail address gives some of it away. `ldapsearch' is good if y…
> Everyone should know enough about LDAP to build a login service that binds against it for internal apps. You can exploit the groups the sys admins maintain to control permissions in your app. It's very powerful and an easy way to get up an running in no time.
Sure, if you want to be the next SolarWinds.
Re: Figure out who's leaving the company: dump, diff, repeat
#189Earlier quoted context omitted.
I worked at a large web dev company and for years they had this attitude. Then one designer put in his two weeks and spent the majority of the time downloading all the site files for all of the sites the company had built over the two years he was there. We're talking hundreds of static sites where he took the all the design docs and static HTML/CSS/JS files one would need to recreate them somewhere else. Instead of…
> You put in your two weeks? Nah, you're out the moment you hit send on that email. Manager alerts security, who then come over to your desk. You get your jacket and whatever you walked in with and get walked out. This will work for the first 5-10-20 people, then word of mouth goes out about this policy and your evil designer is downloading everything the day before sending their resignation mail.
Or “your sales guy is making a little backup of the leads from the CRM before handing in notice”.
Though with sales orgs I think this is almost an expected practice - sales people are often hired on the tactit, never officially acknowledged basis that they will bring their leads list.
Re: Figure out who's leaving the company: dump, diff, repeat
#190Earlier quoted context omitted.
It was there when I left several months ago, so I assume so. Or maybe I shouldn't, they started shuttering a lot of these kinds of things after layoffs.
It's still there, just used it to see if I had guessed right on Rachel's workings (I hadn't). Thanks for making a very useful tool!
Just in case you meant otherwise Epitaphs is not my tool, but I agree it is very useful :)