From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (syn-045-059-245-186.biz.spectrum.com [45.59.245.186]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 930C03CB37 for ; Wed, 18 Dec 2024 10:27:40 -0500 (EST) Received: from dlang-mobile (unknown [10.2.3.133]) by mail.lang.hm (Postfix) with ESMTP id 995A11E8F71; Wed, 18 Dec 2024 07:27:39 -0800 (PST) Date: Wed, 18 Dec 2024 07:27:39 -0800 (PST) From: David Lang To: David Collier-Brown cc: bloat@lists.bufferbloat.net In-Reply-To: <71a37a60-315f-459b-afd7-b431b862cba3@rogers.com> Message-ID: References: <71a37a60-315f-459b-afd7-b431b862cba3@rogers.com> MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="===============6782799599462440524==" Subject: Re: [Bloat] US Weighs Banning TP-Link Router X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2024 15:27:40 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --===============6782799599462440524== Content-Type: text/plain; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT tp=link is in the process of splitting off their US operations (I was looking at getting a job there), which would seem to bypass this problem. David Lang On Wed, 18 Dec 2024, David Collier-Brown via Bloat wrote: > Date: Wed, 18 Dec 2024 10:04:52 -0500 > From: David Collier-Brown via Bloat > Reply-To: David Collier-Brown > To: bloat@lists.bufferbloat.net > Subject: Re: [Bloat] US Weighs Banning TP-Link Router > > 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 > > > 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 >> >> >> 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 >> >> >> >> -- >> 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 > > --===============6782799599462440524== Content-Type: text/plain; CHARSET=utf-8 Content-Transfer-Encoding: BASE64 Content-ID: <982nooo3-92r0-son1-42qq-q5n45ns0n02n@ynat.uz> Content-Description: Content-Disposition: INLINE X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQmxvYXQgbWFp bGluZyBsaXN0CkJsb2F0QGxpc3RzLmJ1ZmZlcmJsb2F0Lm5ldApodHRwczovL2xpc3RzLmJ1ZmZl cmJsb2F0Lm5ldC9saXN0aW5mby9ibG9hdAo= --===============6782799599462440524==--