| Deutsch English Français Italiano |
|
<t2lmljp0l4krqj1gibee87jme141m0efmp@4ax.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!Xl.tags.giganews.com!local-2.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 12 Dec 2024 21:31:41 +0000 From: Joe Gwinn <joegwinn@comcast.net> Newsgroups: sci.electronics.design Subject: Re: Win11 explorer bug? Date: Thu, 12 Dec 2024 16:31:05 -0500 Message-ID: <t2lmljp0l4krqj1gibee87jme141m0efmp@4ax.com> References: <13vgljdqp79a2onuijph2om08fk99u2fdm@4ax.com> <vjablv$14se5$1@dont-email.me> <addhljp8i0d5t42lavnd37a8e883ijhsqt@4ax.com> <vjaeii$14se5$2@dont-email.me> <gquhljd83745shtckfjgtd5u6iphkprprc@4ax.com> <vjblle$1fd6a$1@dont-email.me> <gsnjljdvnhu7m25ops26ek9lvca5eqvk2n@4ax.com> <vjec62$22pn8$1@dont-email.me> <vjefoe$23fh4$1@dont-email.me> <uj2r2lxum3.ln2@Telcontar.valinor> <vjennd$24vi6$1@dont-email.me> <vjf008$2flf4$1@dont-email.me> <sbor2lxim3.ln2@Telcontar.valinor> User-Agent: ForteAgent/8.00.32.1272 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 49 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-tKK2DGPLTdjD96F1Sh703UDX/ZeJsswsKuNqVn9ThZ5Uj4qAUGF1GD0RPbbSfHt3t9XXNqzb15h47EA!G5S+FY8FKQFRtXgWi7atxgDpu1TzoGyLql/Jo46XSBQV+d4luyZOkKrWlsq8g5mCDhlCgPg= X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Bytes: 3550 On Thu, 12 Dec 2024 19:58:36 +0100, "Carlos E.R." <robin_listas@es.invalid> wrote: >On 2024-12-12 16:41, Jeroen Belleman wrote: >> On 12/12/24 14:16, Don Y wrote: >>> On 12/12/2024 5:47 AM, Carlos E.R. wrote: >>>> On 2024-12-12 12:00, Don Y wrote: >>>>> Yeah, I'm REALLY eager to turn on the factory's WiFi interface >>>>> for the stove/oven... NOT! >>>> >>>> There are devices that put the actual interface on the phone, >>>> via WiFi. The physical interface has a reduced set of features. >>> >>> Yes. Via a server located at the manufacturer's facility! >>> >>> So, you have the application layer in the appliance, the network >>> stack in the appliance, all of the network infrastructure from >>> your AP to the manufacturer's server, then, back through the phone >>> network, up through the stack in your phone and, finally, through >>> the app to the display. >>> >>> Nothing can go wrong, there, right? <rolls eyes> >> >> Apart from the obvious security and reliability worries, there is >> the issue that the *manufacturer* gets to decide when *your* device >> is obsolete. > >The device has a limited life expectancy, anyway. About 10 years. The >boiler needs replacement of rubber gasket every year or two. There is a >mandatory yearly maintenance visit. With the remote controller, >maintenance visits are every two years, because the remote server >monitors the parameters and decides when a visit is needed. > >So, that convenience is decisive for me. Win win. A dodge occurs to me: Install a simple firewall between external Internet and internal network that hosts such things as cameras and furnaces. Set the firewall to accept only one of a small set of white listed sources, and otherwise not to reply. White lists have the advantage of immunity to attempts from random places. The lack of response if not white listed will defeat most port IP address and scanners, even though the firewall most likely can be hacked if known. Upgrade the firewall from time to time, to sorta keep up with the threats. Joe Gwinn