Toyota: Car location data and videos of 2M customers exposed for ten years • Hacker News Board

Re: Toyota: Car location data and videos of 2M customers exposed for ten years

#311

Post by abfan1127 » Mon, May 15, 2023, 5:06 PM UTC

Scoundreller wrote: post #240

alvarezbjm-hn wrote: post #85

Earlier quoted context omitted.

Clutch disc is much more expensive to replace, BTW. You won't notice if you buy new every other year, of course.

Going on year 15 with a good clutch on a low-end bmw here. Dunno if luck or not, but not a lot of clutch complaints on bmw forums. Their automatics on the other hand…

the biggest opportunity for clutch wear is starting. If you can be easy on the clutch during start, and rev match very well the rest of the shifts, and shift infrequently, (highway miles) they can last a long time. How many miles in 15 years?

Re: Toyota: Car location data and videos of 2M customers exposed for ten years

#312

Post by Shocka1 » Tue, May 16, 2023, 1:48 PM UTC

Reptur wrote: post #14

I hope jailbreaking and disabling this data collection becomes the norm in the future. It is obvious companies do not prioritize the security protecting our data.

As someone who worked for one of the big Japanese auto manufacturers less than five years ago in Infotainment, in the exact domain of what this thread is talking about, I agree wholeheartedly. You all may or may not be surprised about the philosophy behind this. Your data is looked at as their data... In the company I worked for, this was all driven by a small sect of executives in Los Angeles.

This is one of the biggest reasons I left, as I couldn't agree on an ethical level with the decisions around customer privacy.

Re: Toyota: Car location data and videos of 2M customers exposed for ten years

#313

Post by mixmastamyk » Tue, May 16, 2023, 5:16 PM UTC

smeej wrote: post #227

short_sells_poo wrote: post #36

Earlier quoted context omitted.

> Interior images, exterior images, facial geometry, voice recordings, This is an absolutely unbelievable level of privacy intrusion IMO. I 100% support very heavily fining this sort of behavior, otherwise it will continue to proliferate.

Voice recording without explicit consent of all recorded parties is illegal under wiretapping laws in my state, and my state is pretty aggressive about it. I wonder how that factors into this.

Regulators may not have realized. Maybe send an anonymous tip.

Re: Toyota: Car location data and videos of 2M customers exposed for ten years

#314

Post by TheCapn » Wed, May 17, 2023, 8:14 PM UTC

spacebanana7 wrote: post #164

TheCapn wrote: post #134

Earlier quoted context omitted.

So I don't work in automotive domain, but I work in Controls Engineering. Basically everything you just said relates to my work as well, and based on tidbits of anecdotal info I've picked up through various technical forums it sounds like automotive & controls are quite similar in that regard. The dirty truth is often times these domains were designed and chiefly operated by non-software people. Not to say a mechanic…

> Software Engineering as a regulated profession is going to be a necessity as much as civil engineering or electrical engineering has been Wouldn’t it be easier to regulate the quality of software used in critical products? AFAIK similar regulatory standards and certifications exist for aerospace software.

>Wouldn’t it be easier to regulate the quality of software used in critical products?

Sure, but who is responsible/accountable?

Often times I bring this topic up to have a bunch of people looking for gotchas in my overly broad wishful thinking. I don't want Engineers to be a requirement to work in software as a whole. I don't even think being an "Engineer" makes you better in any functional way than your peers. But I do believe in ideas of accountability, responsibility, ownership, and all the legalese involved with taking that seriously.

If the software is holding people's personal info, say to the point where a leak would constitute real risk, I want a Software Engineer stamping the security design to show they follow best practices and the company isn't taking shortcuts. If the software is controlling a robot that could maim someone, I want to know that some intern wasn't the one signing off to say its safe.

We aren't there yet. And there's lots of work that needs to be done to get us there. I recognize that. But I want to keep putting the bug in people's ears to have that thought for the years that come as we watch more software glitches cause harm to people, to the environment.