<div dir="auto"><div dir="auto">There is a big another issue. Even if we work with softMAC driver, it can ignore or override wireless-regdb. <div dir="auto"><br></div><div dir="auto">For example, iwlfifi could advertise, but ignore MCS 9-11 according to LAR decision. More then that, LAR can spread it's logic and disable some channels globally for all systems. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">That's why, for example, if somebody use both QCA and Intel Wi-Fi modules, the last one will force right use it's settings through cfg80211 API. </div><div dir="auto"><br></div><div dir="auto">So there is a huge issue in kernel restrictions and rules, I think. </div><div dir="auto">Where wireless API is mostly developed by... Intel.</div><div dir="auto">More transparency and fairness required there, I think. No kernel module should be able to become a dictator. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">What about a certification process, well, I saw the dark side. </div><div dir="auto">Certification firmwares are very-very-very far from regular firmwares. That's how it works today. </div><div dir="auto">FCC can certify a product, but then it's firmware cold be modified without any control from FCC.</div><div dir="auto">FCC tries to do the best they can with AFC (I think). </div><div dir="auto">But today there are no any mechanisms to </div><div dir="auto">1) Force vendors to use regular firmware for certification</div><div dir="auto">2) Certify firmware updates. </div><div dir="auto"><br></div><div dir="auto">We'll have to invent something about that. </div><div dir="auto"><br></div><div dir="auto"><br><div data-smartmail="gmail_signature" dir="auto">Best regards,<br>Kirill Lukonin</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пн, 4 окт. 2021 г., 19:54 Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank" rel="noreferrer">dave.taht@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Jul 25, 2021 at 7:48 AM Dave Taht <<a href="mailto:dave.taht@gmail.com" rel="noreferrer noreferrer" target="_blank">dave.taht@gmail.com</a>> wrote:<br>
><br>
> Early on in the FLOSS podcast (<br>
> <a href="https://twit.tv/shows/floss-weekly/episodes/638?autostart=false" rel="noreferrer noreferrer noreferrer" target="_blank">https://twit.tv/shows/floss-weekly/episodes/638?autostart=false</a> ) I<br>
> harped on what is basically my biggest issue with the world of IoT -<br>
> home routers only being a tiny subset - being able to fix the stuff<br>
> you bought, and KNOWING that the stuff you bought isn't going to<br>
> betray you. The cell phone universe is about as well handled in this<br>
> department as seems feasible<br>
<br>
I take it back.<br>
<br>
<a href="https://www.vice.com/en/article/z3xpm8/company-that-routes-billions-of-text-messages-quietly-says-it-was-hacked" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.vice.com/en/article/z3xpm8/company-that-routes-billions-of-text-messages-quietly-says-it-was-hacked</a><br>
<br>
>, but the rest... ugh!<br>
><br>
> I know our lists are mostly technically oriented but does anyone know<br>
> of a site, a forum, a slack channel, a linked in group, a faceboook<br>
> group, some legal advisory group... somewhere??, where I, at least,<br>
> could vent in something in a productive direction? I'm very happy to<br>
> finally be in BITAG but that's just about lag.<br>
><br>
> I often look back on our 2015 fcc fight with remorse, as we didn't<br>
> have enough capital to capitalize on it, and I just went back to<br>
> finishing up our research. We knocked 'em down FLAT with that one<br>
> broadside but nobody read the filing itself, just the press release,<br>
> and the vogons got up again, like a tarbaby, and resumed bad<br>
> governance of the future as usual.<br>
><br>
> For the record, if you haven't read:<br>
><br>
> <a href="http://fqcodel.bufferbloat.net/~d/fcc_saner_software_practices.pdf" rel="noreferrer noreferrer noreferrer" target="_blank">http://fqcodel.bufferbloat.net/~d/fcc_saner_software_practices.pdf</a><br>
><br>
> Our proposal buried on page 12:<br>
><br>
> 1. Any vendor of SDR, wireless, or WiFi radio must make public the<br>
> full and maintained source<br>
> code for the device driver and radio firmware in order to maintain FCC<br>
> compliance. The source<br>
> code should be in a buildable, change controlled source code<br>
> repository on the Internet,<br>
> available for review and improvement by all.<br>
><br>
> 2. The vendor must assure that secure update of firmware be working at<br>
> shipment, and that update streams be under ultimate control of the<br>
> owner of the equipment. Problems with compliance can then be fixed<br>
> going forward by the person legally responsible for the router being<br>
> in compliance.<br>
><br>
> 3. The vendor must supply a continuous stream of source and binary<br>
> updates that must respond to regulatory transgressions and Common<br>
> Vulnerability and Exposure reports (CVEs) within 45<br>
> days of disclosure, for the warranted lifetime of the product, the<br>
> business lifetime of the vendor,<br>
> or until five years after the last customer shipment, whichever is longer.<br>
><br>
> 4. Failure to comply with these regulations should result in FCC<br>
> decertification of the existing<br>
> product and, in severe cases, bar new products from that vendor from<br>
> being considered for<br>
> certification.<br>
><br>
> 5. Additionally, we ask the FCC to review and rescind any rules for<br>
> anything that conflict with<br>
> open source best practices, produce unmaintainable hardware, or cause<br>
> vendors to believe they<br>
> must only ship undocumented “binary blobs” of compiled code or use<br>
> lockdown mechanisms<br>
> that forbid user patching. This is an ongoing problem for the Internet<br>
> community committed to<br>
> best practice change control and error correction on safety critical systems<br>
><br>
><br>
> --<br>
> Fixing Starlink's Latencies: <a href="https://www.youtube.com/watch?v=c9gLo6Xrwgw" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.youtube.com/watch?v=c9gLo6Xrwgw</a><br>
><br>
> Dave Täht CEO, TekLibre, LLC<br>
<br>
<br>
<br>
-- <br>
Fixing Starlink's Latencies: <a href="https://www.youtube.com/watch?v=c9gLo6Xrwgw" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.youtube.com/watch?v=c9gLo6Xrwgw</a><br>
<br>
Dave Täht CEO, TekLibre, LLC<br>
_______________________________________________<br>
Make-wifi-fast mailing list<br>
<a href="mailto:Make-wifi-fast@lists.bufferbloat.net" rel="noreferrer noreferrer" target="_blank">Make-wifi-fast@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/make-wifi-fast" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/make-wifi-fast</a></blockquote></div></div>