View Single Post
Old 07-04-2020, 08:53 PM   #720
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by BetterRed View Post
Not really a rant, but seems a good enough place

On the 2nd inst I posted this

Wouldn't you know it, I just got one (false +ve).

Not in a calibre.msi, in the latest 7TT update install. The author already knew about it and his response to the reporter was:

But it won't gain any popularity unless users ignore the alert. It also implies MS gathers statistics on how many people do ignore the alert.
I'm running Win10 Pro. I just got the latest 7TT update, and there was nary a peep from Microsoft Defender. I have no idea why your installation flagged it.

(MS delivers virus signature updates for Microsoft Defender as part of Windows Updates. The latest one happened today. If you have diddled Windows auto update settings, that might be an issue.)

Quote:
Main Point: is there a phrase for that? That is, when you say 'something' has never happened, implying and it probably never will, the 'something' happens soon after.

Self-defeating prophecy came to mind, but i was looking for something catchier - IMO it's not Sod's, Finagle's, or Murphy's Law, they all imply something went awry.
I call thinking that because it hasn't happened, it never will "wishful thinking".

But Sod's, Finagle's or Murphy's Law might apply, because something did go awry. It was your understanding that did so, but same difference.

I actually gave up on third-party A/V in the WinXP days. I was running Symantec Corporate, courtesy of a site license from an employer. (I would not touch the consumer Norton A/V with a stick, but Symantec installed with no problems, ran like a top, and consumed few resources.)

The version I was running reached EOL, and would no longer get signature updates. I would need a new version. And I no longer worked for that employer, and it would be on my dime. The only thing Symantec ever "caught" had been "false positives". I asked myself if I needed third-party A/V and concluded I didn't.

Viruses and malware are infections. Infections have vectors by which they enter the host body. Ward the vector, and block the infection.

The main vector for viruses was email. I used Gmail. My mail store lived online, and I read and replied in my browser. And Gmail had viewers for common attachment types, so possibly infected attachments never reached my machine. I didn't worry about viruses because I'd warded the vector.

The main vector for malware was the browser. I'd used Mozilla code since Mozilla was the name for a Netscape Communications effort to develop the next generation browser suite to replace Netscape Communicator. Most malware attacked IE, and I hadn't used it in years. (And most malware required Admin access to do its dirty work and bounced it it couldn't get it. I created a restricted ID without Admin access to use in XP, and only used an Admin account to do administrative chores.) I didn't worry about malware. I'd warded the vector.

So I dropped Symantec and never missed it.

Win7 and later did what I wished MS had done in Win2K, and made a non-privileged ID the normal normal account. (What needed to be done required a file system with the embedded notion of different users with different permissions and levels of access. NTFS had it. FAT* did not.)

My strategy won't work for everyone. A late friend ran all up A/V on his laptop, But he sway in the Usenet pool, downloading binaries of things like British Dr. Who episodes that hadn't or wouldn't reach the US. Usenet "binary" groups are cesspools, and if I went there, I'd run all up[ A/V too.

For most mere mortals, practicing Safe Hex and being aware of what you're doing makes MS built-in protection entirely adequate.
______
Dennis
DMcCunney is offline   Reply With Quote