Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Re: Win11 explorer bug?
Date: Fri, 13 Dec 2024 22:18:59 -0700
Organization: A noiseless patient Spider
Lines: 68
Message-ID: <vjj4gd$3sa72$1@dont-email.me>
References: <vjg7dh$kf$2@nnrp.usenet.blueworldhosting.com>
 <vjgm11$396oa$1@dont-email.me>
 <vjhupn$1ds9$1@nnrp.usenet.blueworldhosting.com>
 <vji6qd$3jsoc$1@dont-email.me>
 <vjib0c$2u4n$1@nnrp.usenet.blueworldhosting.com>
 <vjii9m$3ltn2$2@dont-email.me>
 <vjiq87$5dl$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 14 Dec 2024 06:19:10 +0100 (CET)
Injection-Info: dont-email.me; posting-host="50ad193a0c17c9bb9ff03ce57c418426";
	logging-data="4073698"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Wp5e7T1xHCTi8r4tvZM0o"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:xOJ2vEb+2tgPy7xBhxc6e3GXvj4=
Content-Language: en-US
In-Reply-To: <vjiq87$5dl$1@nnrp.usenet.blueworldhosting.com>
Bytes: 4088

On 12/13/2024 7:24 PM, Edward Rawde wrote:
> "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vjii9m$3ltn2$2@dont-email.me...
>> On 12/13/2024 3:03 PM, Edward Rawde wrote:
>>> "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vji6qd$3jsoc$1@dont-email.me...
>>>> On 12/13/2024 11:35 AM, Edward Rawde wrote:
>>>>> "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vjgm11$396oa$1@dont-email.me...
>>>>>> On 12/12/2024 7:50 PM, Edward Rawde wrote:
>>>>>>> I'm getting 441 header line too long while trying to reply to Don Y in the other thread so I'm going to leave it there.
>>>>>>>
>>>>>>> Some organizations are obviously doing a lot better then others at cybersecurity.
>>>>>>
>>>>>> <https://www.crn.com/news/security/2024/10-major-cyberattacks-and-data-breaches-in-2024-so-far>
>>>>>>
>>>>>> at least, the ones that we KNOW about...
>>>>>>
>>>>>>
>>>>>
>>>>> They are all large organizations rather than a single location with a single firewall.
>>>>>
>>>>> Large organisations don't have a single individual doing firewall configuration and security for the entire organisation.
>>>>
>>>> No.  They have automated tools doing this work.  No one spends their time
>>>> manually browsing log files.
>>>
>>> You must have worked for may different large organizations to know how they all do things.
>>
>> Yes.  And have colleagues at (or who have consulted with) others.
>>
>>> Did you miss the part where I said I have automated tools (python scripts) to deal with log files?
>>>
>>> I maintain a blacklist of 200,000 IPv4 addresses and networks in otherwise friendly countries.
>>> Doing that manually would be ridiculous.
>>
>> And I rely on a knock sequence.  Who's spending LESS time on maintaining their
>> service?
> 
> Spending less time on cybersecurity will mean lower knowledge and increased risk of compromise.

And, in 40+ years, online, I've lost nothing.  I guess I must be doing
something wrong...

> And it's fun to see where the brute force and other attacks come from.
> 
> Knock sequences aren't very useful outbound. The last phishing site I visited (out of curiosity) didn't require one.

Why would a SERVER be making *unsolicited* outbound connections?

>>
>>>>
>>>>> The ones who have breaches more likely have managers who don't want anything touched if it's working.
>>>>>
>>>>> So the individual who suggests that changes should be made to restrict database connections to nothing other than known IP
>>>>> addresses
>>>>> or networks, rather than having them open to the entire world, is likely to be ignored. This is, of course, just one of the
>>>>> myriad
>>>>> reasons why breaches occur.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
> 
>