[danso]

IIRC, Tesla's civil complaint accuses Tripp of writing "hacking software" but doesn't mention any other effects of the software besides exfiltration of data to unspecified third parties:

https://arstechnica.com/tech-policy/2018/06/tesla-sues-emplo...

> Beyond the misconduct to which Tripp admitted, he also wrote computer code to periodically export Tesla’s data off its network and into the hands of third parties. His hacking software was operating on three separate computer systems of other individuals at Tesla so that the data would be exported even after he left the company and so that those individuals would be falsely implicated as guilty parties.

[sjwright]

From the perspective of a technologist it's clumsy and imprecise language, but it's not wrong.

He wrote code that was explicitly designed to bypass the company's security and treacherously act in a way that caused damage to the company's interests, then he inserted it using other people's security credentials. The only elements missing between what he did and what a "real" hacker might have done is breach a technical security barrier rather than be a trusted employee.

[danso]

I don't begrudge Tesla for portraying facts as damning as possible to the opposing party -- that's what any litigant would do (and should do, I would think, although IANAL), as long as no deliberately false statements are made. So "technically true" is fine by me. But since their investigation is still ongoing, and they haven't felt the need to divulge more specific and damning assertions, then it's fair to consider what's currently left open to interpretation.

"Wrote code" could include a wget cron job. "Bypass company's security" includes literally any activity done without company approval or authorization, including printing out files and putting them in his briefcase and walking out the building without announcing the fact.

No one is really disputing that his alleged acts were "treacherous" to the company, or that they "caused damage to the company's interests" -- that would cover every conceivable form of whistleblowing.

At this point, I don't see what it matters whether it was a "real" hack or not (though it's ironic you mention social engineering, since for too long that has been ignored as a real attack vector). He took info and disclosed it without company approval, now it's up to the courts to decide if that was legitimate and protected whistleblowing.

[sjwright]

No disagreement here.

As to your last sentence, I think it would be difficult to argue that automated and ongoing bulk data exports could ever fit with any definition of whistle-blowing. If he had legitimate concerns, and evidence of those concerns existed in electronic form, he could have simply walked the specific evidence out of the building on a thumb drive.

That being said, we don't know exactly what data was exported, so any speculation (including my own) is rather pointless...

[threeseed]

If you are a whistleblower then by definition you need to bypass the company's security and cause damage to the company's interest.

The real issue is whether he is a legitimate whistleblower not the acts that he did in order to provide the data to journalists.

[manicdee]

What do you want the software to do other than exfiltrate data in order to count as “hacking software”?