I don't know, I'm beginning to think the bans are not really about security...
https://therecord.media/fcc-pushes-ban-on-updates-to-foreign-routers-drones-2029
I don't know, I'm beginning to think the bans are not really about security...
https://therecord.media/fcc-pushes-ban-on-updates-to-foreign-routers-drones-2029
@cR0w This seems like cyber warfare...
... against their own people.
@cR0w Isn't basically every router "foreign made"? I don't think any router is 100% US made.
Seems like they just don't want those NSA zero-days patched.
@cR0w > The agency also extended a deadline for foreign-made drones to continue receiving software and firmware updates to January 1, 2029 from January 1, 2027.
First, I remain curious why so many people write sentences like that which go backwards in time as you progress through the sentence. Financial news is always like that, too. “Price target adjusted to ____ from ____”. Ridiculous.
Second, that reads like the FCC is saying drones *must* receive software updates until at least 2029? My understanding is the opposite.
@cR0w The FCC notice is painful to read. This is my interpretation of it:
2025-12-22: The FCC changes rules to prohibit import of foreign-made UAVs.
2026-01-21: Waivers are issued to allow UAV vendors to continue updating devices already in the US. These waivers expire on 2027-01-01.
2026-03-23: The FCC changes rule to prohibit import of foreign-made routers. Waivers are issued to allow vendors to keep updating routers until 2027-01-01.
2026-05-08: All the waivers’ expiration is pushed back until 2029-01-01, and the division of the FCC which issued them (the OET) is recommending the rules be changed to allow updates forever without a waiver.
Do you know the history of Huawei? They were one of the first companies that triggered warnings over a decade ago about people embedded inside the Chinese government and also associated with Huawei installing software-based backdoors accessible via commonly used ports on Huawei routers. The effort by the US federal government to stop this has further branched out to blocking the import of chips manufactured in China for American-designed IoT devices and routers.
At the present time in cybersecurity with a haphazard US government plugging as many leaks in the form of global and domestic crises and overburdening itself with respect to the Iran War and the situation in the Middle East — two disparate but related elements within the US government can be mutually exclusive — unfortunately. My view about this is they need to form a plan and stick to the plan through using political mechanisms.
The FCC doesn't want back doors around. They are citing existing Import/Export controls [1] and they want to protect (or would /prefer/ to protect, rather) America's intellectual property from being exfiltrated through the software back doors. The White House is for the most part now detached from public reality, sadly. Although the article says that the trump admin is supporting this effort and it does really matter in the end what Donald Trump understands about technology. The President holds the veto pen in Congress.
[1] - "U.S. Commerce Department's Bureau of Industry and Security (BIS) maintains the "Entity List" of blacklisted firms under export control restrictions. This list has grown nine-fold over the last decade to nearly 1,200 entities, as hundreds of companies from China's #Huawei to Russia's Gazprom were added. Executive Order 13783 added Huawei and 68 Huawei affiliates across 26 destinations to the Entity List in May 2019"
@iamnickw You sure seem to give the regime a lot of benefit of the doubt. But this bit made me actually LOL:
The FCC doesn't want back doors around.
The FCC DGAF about that. Do you really think they would have let the telecoms sweep the Typhoons under the rug like they did if they cared about anything security related?
@iamnickw @cR0w Do you know the history of Cisco? It's an usa firm. They repeatedly put hardcoded credentials into their software the user can't change and can't normally see, security researcher finds it and then they patch those "bugs" (or not, if the product is past its EoL).
Here are a few of them, all high or critical severity:
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20180328-xesc.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-csm-rce-8gjUz9fW.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20151104-mse-cred.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-ise-aws-static-cred-FPMjUcm7.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20190313-cspcscv.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-cssm-sc-Jd42D4Tq.html
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ftd-statcred-dFC8tXT5
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-on-prem-static-cred-sL8rDs8.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-rv110w-static-cred-BMTWBWTy.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20160629-fp.html
https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-20170607-dcnm2.html
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cer-priv-esc-B9t3hqk9
Like - there are 76 of those when you search for "Static Credential Vulnerability" at search.cisco.com and narrow it down to bug info category - starting at 2011, ending at 13 February 2026.
How many times could a company reasonably forget about putting hardcoded credentials in their software? Once? Twice? Fuckin' 76 times and probably counting? Doesn't that look dodgy in the slightest? If it doesn't ring a bell, don't really know what would.
A vulnerability in Cisco IOS XE Software could allow an unauthenticated, remote attacker to log in to a device running an affected release of Cisco IOS XE Software with the default username and password that are used at initial boot. The vulnerability is due to an undocumented user account with privilege level 15 that has a default username and password. An attacker could exploit this vulnerability by using this account to remotely connect to an affected device. A successful exploit could allow the attacker to log in to the device with privilege level 15 access. Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability. This advisory is available at the following link: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180328-xesc This advisory is part of the March 28, 2018, release of the Cisco IOS and IOS XE Software Security Advisory Bundled Publication, which includes 20 Cisco Security Advisories that describe 22 vulnerabilities. For a complete list of the advisories and links to them, see Cisco Event Response: March 2018 Semiannual Cisco IOS and IOS XE Software Security Advisory Bundled Publication.
@cR0w Putting the squeeze on #RootInfractructure by #TechBros and their #USpol cronies, goes hand-in-hand/Venn's to major trade routes like China, and other artificially manufactured opposition. Further entrenchment of false amplification of direct opposition, keeps subservience in place to serve #Capitalism #greed.
Break the fake. Graduate the #brainwashing. Replace #AbusivePower with ethical #RootInfrastructure #scientists.
@the_turtle @cR0w THIS, for every single thing. Giving too much credit to a decaying, old, orangey common thief trying to set up his family by common bribery.
The people taking advantage of the situation by using their bribe-rights, those are the ones messing all up.
@cR0w If they were serious, they’d be banning the cheap WiFi cameras. My MiL bought us a bird feeder with an AICam and requires an app. Everything goes thru China, except the subscription payments (Shopify, iirc) and even that might.
The Eufy security cam I bought was better in that it talks to US AWS servers, but still an update could easily send it all back to China.
These things could easily do DDoS attacks and much more
The CRA in the EU, when it goes live, will do this. All those products have known security exploits and you won't be allowed to sell products that has that.
... if things work out as we hope ...
@FurryBeta @cR0w "These things could easily do DDoS attacks and much more"
*coughMiraicough*