Live data from Hacker News

Elon Musk emails employees about 'extensive and damaging sabotage' by employee

cnbc.com

591–600 of 627 posts

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#591

> As you know, there are a long list of organizations that want Tesla to die. Is it correct to use 'are' here instead of 'is'?

UK vs. US English. We (English people) say "The Football Team are playing well", for instance.

I'm still not sure. I discussed this topic with my English teacher (he's from the UK) yesterday and he does not like how this phrase looks either.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#592
post #326

Earlier quoted context omitted.

They haven’t been accused in this case, so let’s not get ahead of ourselves.

Maybe not accused directly but Musk's email seems to heavily imply it.

Hardly. Stating that something is a possibility that is worth looking into is not anything close to implying that that thing is necessarily the case. This is basic critical thinking 101.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#593
post #84

Earlier quoted context omitted.

This is a very naive comment. There will always be a small handful of engineers that can push the button to move code into PROD or even change code in PROD live. Ideally, with mature controls, the people in this list is short. But to jump to the conclusion that Tesla doesn't use good practises is very short sighted. Who's to say that external parties didn't target this person specifically because of their role/influe…

>There will always be a small handful of engineers that can push the button to move code into PROD or even change code in PROD live. What? Why? Nobody on my development team has access to the production code signing keys. And nobody - at all - has the ability to remotely make a production system take an unsigned update.

Heh Heh Heh

You know that backup system your production servers have?

That also has perfect _write access_ to everything, and it's needed so _restoring_ after something goes wrong works.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#594

> As you know, there are a long list of organizations that want Tesla to die. Is it correct to use 'are' here instead of 'is'?

It depends on which part of the sentence you would like to emphasise. In this case, the _organisations_ want Tesla to die, not the _list_. Hence the plural form. Not all collective nouns work this way, but in this case either is grammatically correct.

But the words order is unambiguous (for me at least). I need to read about this topic more closely though.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#595

Earlier quoted context omitted.

Ok, but we are trusting this 'young and rambunctious' company to produce software for self driving cars, where lack of appropriate policy controls could result in serious consequences if another "disgruntled employee" decides to sabotage the codebase

Really, the most worrisome aspect of this story isn't the alleged sabotage: it's that a single unauthorized employee was able to make such widespread changes to the software. Says horrible things about Tesla's security policies, especially for a company claiming that it will unleash true self-driving sometime in the next 6 months.

Move fast and break things.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#596
post #546

Earlier quoted context omitted.

Sure, but he seems very eager to steer the thing towards external interests and sabotage rather than this being an isolated incident. Sounds to me that he is fishing for scapegoats in general...

I read it as a general motivational tactic. Everyone else is out to get us. We need to pull together. They want us to fail, let's prove them wrong. From coaches or CEOs. This is essentially newspaper clippings in the locker room.

Yeah it's quite different to the leaked email Tim Cook has sent to his employees.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#597
post #565
post #562

Earlier quoted context omitted.

So what are the odds then that they created a new user account on some local machine and used that to make the changes?

If we're talking about changes to the software that's used to manufactures vehicles that are driving on public roads, I sure as hell hope the odds are zero.

I hope so too, but then again we constantly read stories where serious industrial equipment and critical infrastructure has their computer systems opened up to the wide Internet because someone thought they would like to control it from a crappy app on their phone. Etc.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#598

> This included making direct code changes to the Tesla Manufacturing Operating System under false usernames and exporting large amounts of highly sensitive Tesla data to unknown third parties. How do "false usernames" work in a modern development environment where all commits are tied to a single real-world user?

I've already said this, but there were no malicious code changes, rather malicious and deliberate misconfiguration of the software.

I'm having trouble seeing a difference between the two.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#599
post #487

Perhaps they should have better security measures? If I understand correctly, Tesla cars can be updated OTA including critical functions, so someone who manages to insert a malicious software update might be able to kill everyone driving a Tesla at some moment, plus numerous bystanders.

Language nitpick: I think you mean anyone, not everyone.

Re: Elon Musk emails employees about 'extensive and damaging sabotage' by employee

#600
post #584

Earlier quoted context omitted.

We used to do this at LAN parties in the 90s... of course goatse was the preferred background. People quickly learned never to leave their seats for more than 30 seconds. Most people would just do a 5-10 minute power-nap in their chairs.

Why not simply lock the screen?

AFAIK lock screen ability was only available on Windows NT and we were all running Windows 95/98 which didn't have a workstation lock feature.
Post reply on HN