Deutsch   English   Français   Italiano  
<uvnio7$eac$1@nnrp.usenet.blueworldhosting.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder6.news.weretis.net!newsfeed.hasname.com!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: "Edward Rawde" <invalid@invalid.invalid>
Newsgroups: sci.electronics.design
Subject: Re: Re:Predictive failures
Date: Wed, 17 Apr 2024 00:21:24 -0400
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Lines: 53
Message-ID: <uvnio7$eac$1@nnrp.usenet.blueworldhosting.com>
References: <uvjn74$d54b$1@dont-email.me> <uvjobr$dfi2$1@dont-email.me> <uvkn71$ngqi$2@dont-email.me> <uvkrig$30nb$1@nnrp.usenet.blueworldhosting.com> <uvl2gr$phap$2@dont-email.me> <uvm7f5$pvu$1@nnrp.usenet.blueworldhosting.com> <uvmaet$1231i$2@dont-email.me> <uvmca4$up7$1@nnrp.usenet.blueworldhosting.com> <uvmjmt$140d2$1@dont-email.me> <uvmkco$2fih$1@nnrp.usenet.blueworldhosting.com> <uvmqve$15hl7$2@dont-email.me> <uvmthn$bjm$1@nnrp.usenet.blueworldhosting.com> <uvn7lm$17so6$2@dont-email.me> <uvn96o$2o0t$1@nnrp.usenet.blueworldhosting.com> <uvnf00$1cu2a$1@dont-email.me>
Injection-Date: Wed, 17 Apr 2024 04:21:27 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="14668"; mail-complaints-to="usenet@blueworldhosting.com"
Cancel-Lock: sha1:EPctNHc3yYoTc1fsM14vC4Vd1So= sha256:swT/DXyhNxk3IX/IyV+BnGdUGE7SX2oUNFtCQNr8WVc=
	sha1:fW39NnHpcj1GeOeV75ut2ZMtXWI= sha256:uMNCr5HHu6sJ36Y5AJOVCAMq3Qkp4MTcCRUMvoRvdNs=
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-Priority: 3
X-RFC2646: Format=Flowed; Response
Bytes: 3696

"Don Y" <blockedofcourse@foo.invalid> wrote in message 
news:uvnf00$1cu2a$1@dont-email.me...
> On 4/16/2024 6:38 PM, Edward Rawde wrote:
>>> Simple solution:  router has no radio!  Even if the appliances wanted
>>> to connect (ignoring their "disable WiFi access" setting), there's
>>> nothing they can connect *to*.
>>
>> I'd have trouble here with no wifi access.
>> I can restrict outbound with a firewall as necessary.
>
> I have 25 general purpose drops, here.  So, you can be in any room,
> front/back porch -- even the ROOF -- and get connected.

I have wired LAN to every room too but it's not only me who uses wifi so 
wifi can't be turned off.

>
> The internal network isn't routed.  So, the only machines to worry about 
> are
> this one (used only for email/news/web) and a laptop that is only used
> for ecommerce.

My LAN is more like a small/medium size business with all workstations, 
servers and devices behind a firewall and able to communicate both with each 
other and online as necessary.
I wouldn't want to give online security advice to others without doing it 
myself.

>
> I have an out-facing server that operates in stealth mode and won't appear
> on probes (only used to source my work to colleagues).  The goal is not to
> look "interesting".

Not sure what you mean by that.
Given what gets thrown at my firewall I think you could maybe look more 
interesting than you think.

>
> The structure of the house's fabric allows me to treat any individual
> node as being directly connected to the ISP while isolating the
> rest of the nodes.  I.e., if you bring a laptop loaded with malware into
> the house, you can't infect anything (or even know that there are other
> hosts, here); it's as if you had a dedicated connection to the Internet
> with no other devices "nearby".

I wouldn't bother. I'd just not connect it to wifi or wired if I thought 
there was a risk.
It's been a while since I had to clean a malware infested PC.

>
>