8 ms·
Wait, they got in through take-home leetcode tests? That’s damn clever. I program Apple software, and Xcode projects can dig deep. Apple gives you a warning a
by ChrisMarshallNY 3y ago
Wait, they got in through take-home leetcode tests?
That’s damn clever.
I program Apple software, and Xcode projects can dig deep. Apple gives you a warning about opening a downloaded project, but you’re almost certain to ignore that, if you think it’s a take-home.
I assume that taking online ones would ask for hairy access, as well.
Also, the people going for these would probably have pretty damn good access to the corporate Crown Jewels.
Of course, no one would use corporate resources for job-hunting, right? I know that folks here, get all huffy, when I suggest that happens rather frequently.
- macintux 3y agoAt my first IT job, I spotted some bounce messages from a jobs address at a local big pharma firm. Admittedly, personal email addresses weren’t as common in 1996 as they are now, but still, rookie mistake. I’ve maintained a strict “don’t do anything personal on a corporate computer” policy for a long time, but I’ve not found that to be a common approach.
- ryandrake 3y agoSame here. Air gap your personal and professional life. Separate devices, separate networks (if you work from home), don’t even bring your personal device to work if you don’t really have to. There was a story a few years back making the rounds on HN where an Apple employee had to turn in her corporate device due to some lawsuit against the company. This happens all the time in big companies. She was outraged at this because she had personal nudes on her corporate device. WTF how could anyone think this was a good idea?
- WWLink 3y agoI don't work for Apple or (honestly) know anyone that does, but from at least one news article, I get the impression Apple openly encourages (and maybe even requires) it. https://www.theverge.com/22648265/apple-employee-privacy-icloud-id https://www.theverge.com/22648265/apple-employee-privacy-icl...
- steelframe 3y ago> I get the impression Apple openly encourages (and maybe even requires) it. When I worked at Apple I needed a personal iCloud account to set up my corp MacBook. I simply created a new dummy personal account just for that. Nobody's auditing your iCloud account to make sure it's your "real" personal account or anything.
- raverbashing 3y agoYeah about that. That's one of the biggest weirdness in related to Macbooks on a corp environment, why do I need an unrelated account to do basic stuff on an Apple machine
- WWLink 3y agoIt all depends on how they manage them. You can and should just make a youremail@company.com icloud account. I'm actually surprised that's not the norm so they can take over stuff like activation lock. I don't use a personal icloud account on my work computer... it's not even allowed lol.
- emodendroket 3y agoI have a “work personal” Google account for Chrome for similar reasons.
- xmodem 3y agoAt my last job I used a dummy iCloud account at the system level, but you can log into a separate account for the app store, which was necessary to avoid having to re-buy some apps I depend on. Just as I was leaving they were in the process of replacing everyone's computer with new ones that were much more locked down.
- otteromkram 3y ago[flagged]
- 3y ago
- Scoundreller 3y ago> There was a story a few years back making the rounds on HN where an Apple employee had to turn in her corporate device due to some lawsuit against the company. Smarter decision is for the corp to just buy your device for you. Then it's a personal device, and at least in some cases I'm aware of, not a government record at least. Very doable for a phone where your "work" is limited to messages, webmail and calls.
- MandieD 3y agoMy advice to young colleagues: never do anything on a work computer that you wouldn’t mind your boss (or her boss) seeing. Being greeted with a Department of Defense splash screen before login reminding me that everything I did on that computer was subject to monitoring formed that habit early, and I still can’t shake it, no matter how long I work in Germany, for a German firm with a rather assertive works council.
- Aqua_Geek 3y agoWhenever I grade take-home assignments, the first thing I do is open the Xcode project file in vim and look for shady stuff. Admittedly, I don’t think most of my colleagues do the same due diligence.
- deleted 3y ago[deleted]
- saagarjha 3y agoApple added sandboxed shell scripts recently, I assume as part of an effort to make builds a little more hermetic. While I’m sure it’s not a perfect solution I feel like it would be nice to open a project in a mode where all build steps run in a sandbox. Obviously when something fails you can take a look at what it was trying to do :)
- jetti 3y ago>Of course, no one would use corporate resources for job-hunting, right? I know that folks here, get all huffy, when I suggest that happens rather frequently. Where I work we have a take home exercise we have candidates do and then when we have the interview with that person we review their code with them and ask them to make incremental changes to see how they handle the asks with their communication skills and their technical ability. I interviewed one individual who couldn’t even get the REPL started for their project and as they were struggling trying to get it to work I heard them mumble to themself “I should have just use my work computer”. The fact they couldn’t get the most basic aspect of the project to work on their personal meant that they did their coding assignment on their work computer
- beebeepka 3y agoInteresting. What makes work provided computers better suited for coding? Me, I don't recall using company hardware for anything even remotely personal in many years. It's stupid because they are loaded with all kinds of spyware.
- jrumbut 3y agoJust that it's set up in a particular way, I suspect. A long running project/organization will accrete plenty of tools, scripts, configurations, etc that make their environment different than another using a similar stack.
- jasonwatkinspdx 3y ago> Interesting. What makes work provided computers better suited for coding? Some people only know how to code within the environment managed by their corporation. This is increasingly the case with folks that have only worked at Kubernetes shops.
- otteromkram 3y ago[flagged]
- Grimburger 3y ago> no one would use corporate resources for job-hunting Morally grey(pale blue?) aside, I've been given entire days at work to look for new jobs as part of a redundancy agreement, it was widely supported by management.
- quickthrower2 3y agoDownload an .exe, but via an appeal to greed and flattery, and implied trust ofa FAANG. The solution might be to do real work in VMs while the laptop is a dumb terminal then lock it the fuck down (no downloads!)
- deleted 3y ago[deleted]
- emodendroket 3y agoSeems like a silly, unnecessary risk but it seems like more and more people don’t even have their own laptop.
- pjmlp 3y agoIn many companies using work laptops for private stuff is considered a security issue and a breach of work contract, not everyone actively checks it, it is however an easy way to fire someone when something like this happens.
- namdnay 3y agoPersonally I gave up having my own computer about 10 years ago. Probably not the “safest” strategy, but I always found it a bit wasteful to buy a second device.
- pjmlp 3y agoI have worked in companies where that would be a reason to cease contract.
- ahoka 3y agoWe had someone submit their current employers code as a solution to the assignment. It had the company’s name all over in namspaces, etc. It was also not what we asked for, but something only slightly related. Their employer was making medical devices.
- 3seashells 3y agoEverything cooperate devices touch the own, so if you hunt for a job on company property you become a consultant in your next job leased out by your current one. u/s@
- francisofascii 3y agoCoprporate laptap for personal use, No, but corporate monitors and dock, Yes.
- hddqsb 3y agoThe attackers didn't even use a trojan project/source. They just sent a malicious .exe (wrapped in an .iso file) and asked the victim to run it and write a C++ program that produces the same output.