Live data from Hacker News

Volkswagen blocks Home Assistant by requiring client assertion

github.com

71–80 of 203 posts

Re: Volkswagen blocks Home Assistant by requiring client assertion

#71
post #64

Client Assertion is an OAuth feature, but that is not at all what is being discussed here, if anyone else was confused. It is only present in the HN title and is not mentioned on the page.

The apps now require the use of "Security Assertion" from the client.

In this case, it's by Play Protect on Android, and whatever they use on iOS.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#72
post #60
post #56

What does client assertion mean here? I don't see any mention in the GitHub issue.

It means that the request to the API contains cryptographic proof that is was generated by a legitimate, reviewed app running on a unmodified and non-rooted mobile device controlled by Apple or Google.

fwiw this is a correct definition of Remote Attestation, matching what is mentioned in the github thread, but Client Assertion is something mostly unrelated (an OAuth implementation detail)

Re: Volkswagen blocks Home Assistant by requiring client assertion

#73
post #61

Earlier quoted context omitted.

Volvo is also doing pretty good with offering an official API

Volvo also has the fully mandatory requirement of a consumer Google Account to use the vehicle now due to how tightly integrated Google Automotive is.

You can still use the infotainment without signing into a Google Account. The only thing that's locked out is the Play Store and 3rd party apps (which you need the play store to download).

Even Google Maps is usable without an account.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#74
post #5

There needs to be a law that makes remote attestation - no matter who provides the root certificates, Google/Apple/GrapheneOS - illegal. There is only one use for this technology right now, and it is to prevent people from doing what they want to do with the devices they own, while also making interoperability cryptographically impossible. This is anti-competitive and should simply be illegal.

> There is only one use for this technology right now, and it is to prevent people from doing what they want to do with the devices they own.

Well, that and making it possible to deploy devices you own in environments where they might be physically accessible to people you don't want extracting credentials from them. Or for ensuring people can only access sensitive company information on company issued devices rather than being able to casually make a copy of any data they have access to somewhere else. Or using a phone as a credit card payment terminal without the possibility of displaying one payment amount on screen and authorising for a different amount.

I'm quite firmly in favour of anything I own giving access to the data it's generating in an open format but screaming about how there's no legitimate use for attestation is quite simply nonsense.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#75
post #51

Sad to see some people still believe raw capitalism works and that they can "vote with their wallet".. but they don't see that all car manufacturers can just agree to enshittify their products the same way and use their position to ensure you won't just "start your own car company". There's no real choice and those in power don't care. Only regulation can help.. or a revolution in case the political system in your co…

Anti-competitive practices that you describe ("all car manufacturers can just agree") is definitely not a capitalistic thing (market competition being an important part of capitalism), and indeed regulation can improve the bad outcomes.

I think revolutions are more successful when there is some new idea of what to replace the system with. Currently I did not see anything remotely interesting (ex: french revolution came with the new idea of equality before the law, which was not the case before), and I think is mostly due to low overall education - you can't improve a system if most of the people do not think about complex issues like laws, taxes, efficiency, etc. Everybody loves to point a finger at someone and blame them (immigrants, rich people, woke people, etc.) like that would "miraculously" solve any issue.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#76
post #58

Seems doubtful that this security will be very strong. It won't be hard to spoof an official client.

If they’ve done it using Secure Enclave it’s essentially physically impossible to spoof.

Wouldn’t any Volkswagen keys need to cross the network to get into the Secure Enclave? Or couldn’t you exploit the Volkswagen app itself?

Re: Volkswagen blocks Home Assistant by requiring client assertion

#77

/me scratches VAG cars from a possible new EV purchase. I hate Elon as much as the next guy, but Tesla is still playing the API game way better than the rest of the pack (even with the "not so new" Tesla Fleet API change)

Fleet api kinda sucks, but esphome via ble is solid. Even managed to connect $10 macropad so kids in back can control music.

That's pretty brave.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#78
post #30

I mean, it was founded by the Nazi party, they single handedly destroyed diesels through the world's largest scam, what ethics can you really expect from them? I find it extremely funny when people boycott Teslas for being "Nazi" but won't boycott actual Volkswagens that was founded by the real Nazi party and to date - followed some of the most unethical practices in automative history :)

This is not an intelligent comment. the Nazi parry and modern-day Volkswagen have nothing in common, whereas Tesla is currently^ actively^ run by someone morally reprehensible to many. If you had any actual understanding—:as opposed to just hearing this little factoid in passing and have been waiting for every opportunity to whip it out— you’d know that already. It’s funny as a quip, but don’t for a a second act like…

Stop pasting LLM replies through fake accounts. Dieselgate happened very recently (in this decade). Just research your stuff before you slap a prompt onto an LLM please.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#79

Quite a few other manufacturers have done the same thing. I use a reverse engineered Polestar library to get charging status but I'm in the middle of building a CANBUS sniffer to do the same job because I don't trust they won't do the same thing as this. I don't really understand it, it doesn't seem to offer a huge potential revenue stream and it pisses off the people who are most invested in your product.

This is kind of an interesting contrast with BSH (Bosch and Siemens home appliances ), who are also German.

They appear to have seen making their Home Connect platform open as at least in part a matter of compliance with EU data transparency and portability laws.

Re: Volkswagen blocks Home Assistant by requiring client assertion

#80
post #5

There needs to be a law that makes remote attestation - no matter who provides the root certificates, Google/Apple/GrapheneOS - illegal. There is only one use for this technology right now, and it is to prevent people from doing what they want to do with the devices they own, while also making interoperability cryptographically impossible. This is anti-competitive and should simply be illegal.

> There is only one use for this technology right now, and it is to prevent people from doing what they want to do with the devices they own. Well, that and making it possible to deploy devices you own in environments where they might be physically accessible to people you don't want extracting credentials from them. Or for ensuring people can only access sensitive company information on company issued devices rather…

> Or using a phone as a credit card payment terminal without the possibility of displaying one payment amount on screen and authorising for a different amount.

It only attests that the device booted normally (locked bootloader, factory firmware, etc.). Any kind of post-boot compromise (whether it's from malware or something user-initiated) goes completely undetected and does not impact attestation status.

Post reply on HN