I would hope that this becomes relatively simple at some point.
1. I have this box that says I get updates until 2025-01-01.
2. It is 2023-09-05.
3. I have applied all available security updates.
4. Vulnerability X is still exploitable and has been made public to the manufacturer for 4 months.
5. Get full refund for defective product.
Obviously we are a long way from this. Especially 4 being hard to make a concrete rule for.
So companies would be forced to disclose their actual level of support, and risk consumers not wanting the product, lie on their disclosure and risk a significant class-action lawsuit, or improve their level of support.
I would hope the market would tip us towards the latter scenario, but...we won't know unless we actually force disclosure of these things.
While I think this is true, there's also some benefit to getting the manufacturer's to pay lip-service to the idea.
In that, it becomes part of the marketing and the sales of the device. Later, consumers can _attempt_ to hold manufacturer's feet to the fire with false advertising and other fraud class action lawsuits.
It's really really not a good system, but even forcing a bit of lip-service is a marginal improvement over what we have now.
> Therefore, the most meaningful step would be to require support for open-source firmware.
I agree that it would absolutely be better, but it sounds like even this voluntary labeling program is the compromise that might be tolerated by the other members of the FCC. I'm guessing such a strong and effective program would be a non-starter with those members.
Which, honestly, tells me a lot about the other members of the FCC, and whose interests they are seeking to serve.