General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] US Weighs Banning TP-Link Router
Date: Wed, 18 Dec 2024 10:04:52 -0500	[thread overview]
Message-ID: <71a37a60-315f-459b-afd7-b431b862cba3@rogers.com> (raw)
In-Reply-To: <a4c3d527-2d39-4f34-8a75-fe40e9e843db@rogers.com>

[-- Attachment #1: Type: text/plain, Size: 2446 bytes --]

Previous claims, from August 2024:

therecord.media

Routers from China-based TP-Link a national security threat, US 
lawmakers claim <#>

The two members of Congress called on the Commerce Department to 
investigate risks related to TP-Link routers amid concerns over 
state-backed Chinese hacking operations.

🔗 
https://therecord.media/routers-from-tp-link-security-commerce-department 
<https://therecord.media/routers-from-tp-link-security-commerce-department>

On 12/18/24 09:54, David Collier-Brown via Bloat wrote:
>
> I see, from Slashdot, that the US is considering banning TP-Link 
> routers, as a security risk.
>
> Most can run OpenWRT: should we be petitioning the Commerce Department 
> or it's equivalent to require existing TP-Link routers be migrated to 
> OpenWRT? And I'd suggest, while /retaining their settings/.
>
> --dave
> (I used to do fixed-price source-to-source ports at Sun, so this is 
> possible)
>
> news.slashdot.org
>
> US Weighs Banning TP-Link Router Over National Security Concerns - 
> Slashdot <#>
>
> U.S. authorities are investigating Chinese router manufacturer TP-Link 
> over national security risks and considering banning its devices, WSJ 
> reported Wednesday, citing sources familiar with the matter. The 
> Commerce, Defense and Justice departments have launched separate 
> probes into the company, whic...
>
> 🔗 
> https://news.slashdot.org/story/24/12/18/1249207/us-weighs-banning-tp-link-router-over-national-security-concerns 
> <https://news.slashdot.org/story/24/12/18/1249207/us-weighs-banning-tp-link-router-over-national-security-concerns> 
>
>
> www.msn.com
>
> MSN <#>
>
> 🔗 
> https://www.msn.com/en-us/money/markets/u-s-weighs-ban-on-chinese-made-router-in-millions-of-american-homes/ar-AA1w51es 
> <https://www.msn.com/en-us/money/markets/u-s-weighs-ban-on-chinese-made-router-in-millions-of-american-homes/ar-AA1w51es> 
>
>
>
> -- 
> David Collier-Brown,         | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net           |              -- Mark Twain
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |              -- Mark Twain

[-- Attachment #2: Type: text/html, Size: 7150 bytes --]

  reply	other threads:[~2024-12-18 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4c3d527-2d39-4f34-8a75-fe40e9e843db.ref@rogers.com>
2024-12-18 14:54 ` David Collier-Brown
2024-12-18 15:04   ` David Collier-Brown [this message]
2024-12-18 15:27     ` David Lang
2024-12-18 15:43       ` David Collier-Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=71a37a60-315f-459b-afd7-b431b862cba3@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox