Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Honda Civics and the Evil Valet

juniperspring.org

Post reply on HN
Print view View original

1–10 of 105 posts

Re: Honda Civics and the Evil Valet

#2

Post by librick »

To update 10th-gen Honda Civics, Honda ships updates on specially-formatted USB drives. They're essentially Android 4.2.2rc1-era recovery packages with some Honda-added version checks (which can be spoofed). The packages are signed with the publicly-known AOSP test key, so with physical access to the front USB port you can sign and flash your own package for arbitrary code execution on the headunit. This doesn't require root/su. I've run it end-to-end on my own 2021 Civic and separately confirmed an official EU update file carries the AOSP test-key signature. Tooling and writeup in the post.

Re: Honda Civics and the Evil Valet

#7

Post by hankbond »

Seeing more and more projects eschew code docs with the idea that "well architected code can be queried by LLMs" and stick to more functional runbook style docs. It really is unlikely that at any given point all of the docs of a project are up to date with the code.

I'm generally aligned with this, but it is predicated on the whole "well architected" code part.

Re: Honda Civics and the Evil Valet

#8

Post by jmalicki »

hankbond wrote: post #7

Seeing more and more projects eschew code docs with the idea that "well architected code can be queried by LLMs" and stick to more functional runbook style docs. It really is unlikely that at any given point all of the docs of a project are up to date with the code. I'm generally aligned with this, but it is predicated on the whole "well architected" code part.

I'd rather see unit tests as documentation.

The test can show intended use, show interesting corner cases, and I know it is up to date because it is constantly running and passing.

I think that is a huge underrated benefit of adding a lot more testing.

If I think a developer is going to ask a question of how something works, or about a corner case, isn't that deserving of a test, so they can just see proof of the answer to their question immediately rather than trying to re-derive it?

Re: Honda Civics and the Evil Valet

#10

Post by EPWN3D »

jmalicki wrote: post #8
hankbond wrote: post #7

Seeing more and more projects eschew code docs with the idea that "well architected code can be queried by LLMs" and stick to more functional runbook style docs. It really is unlikely that at any given point all of the docs of a project are up to date with the code. I'm generally aligned with this, but it is predicated on the whole "well architected" code part.

I'd rather see unit tests as documentation. The test can show intended use, show interesting corner cases, and I know it is up to date because it is constantly running and passing. I think that is a huge underrated benefit of adding a lot more testing. If I think a developer is going to ask a question of how something works, or about a corner case, isn't that deserving of a test, so they can just see proof of the ans…

LLMs are great at writing unit tests.
Post reply on HN