Page 3 of 4

Re: M$ strikes again

Posted: 26 Mar 2014, 07:57
by rohan
rohan wrote:... "Users of Microsoft Security Essentials will also receive the warning through its definition updates." ...
I received a new m$ update notification this morning of an MSE client update. Coming so near the end of support, it's very tempting to think that this "update" is how they will nag us yet again about the end of "life as we know it". Needless to say I'm refusing to install this.

M$ strikes again, and again, and again ...

:cheers:

Re: M$ strikes again

Posted: 13 Apr 2014, 04:41
by mayagrafix
Okey, just updating the status quo: MS Essentials is for the most part, a non sequitur, to wit, since many moons ago it has not been updated and will not protect ur system from most modern virus attacks. They (M$) just gave up on it a long time ago. No matter how many updates it does today, its not enough.

Red Hat (Fedora) seems to be the most protected OS vis a vis recent attacks, ie Heart Bleed. Here is the answer from the Planet Fedora blog:
http://feedproxy.google.com/~r/xenodebl ... crajo.html

In english, as per Google translate:
Announcement: Are We Affected by #HeartBleed ?

Through this article I try to warn amongst other things (because here in Mexico it is a legal obligation to do so) that the already known bug #Heartbleed does not affect any of our servers or machines like that in any way. Anyway the servers and equipment we use have already been updated with the new version of OpenSSL that includes the hotfix indicated to repair the vulnerability (and long available thanks to the effectiveness of the community packagers and developers behind the Fedora Linux, the SO we run on our computers/servers) and because in the future if we managed to take some direct implementation of SSL on our sites (which you interact with it) no one will be affected by this security hole.

Unfortunately, other services and sites that have nothing to do with us directly (but who are used in our website for example) themselves have been affected by this bug. Services third party to deal in the web/blog and "cloud" Xenode Systems (for calling somehow the digital ecosystem with you and we interact on par) and yes they were affected by the Bug Heartbleed are as follows :

Facebook
SpiderOak
GitHub
UbuntuOne


Other services that are used on the page (for login with OmniAuth for example) that were POSSIBLY affected are Twitter ( Those who have not reported) Google Accounts (Who has not said either yes or well but probably not yes they have been affected).

here is the XKCD answer:
Image

Re: M$ strikes again

Posted: 14 Apr 2014, 17:20
by DaveB
For info.. the latest MSE update issued today is the one that will install the EOL warning telling you effectively that MSE no longer supports XP. No alternative as far as I can see but to uninstall MSE and find something willing to hang on in there.

ATB
DaveB B)smk

Re: M$ strikes again

Posted: 01 May 2014, 12:42
by DaveB
Life after EOS for WinXP

It's probably fair to say that come EOS for XP, I'd got most of what I needed on my Win7 system and I moved to that pc unconsciously. It's the system I use most so letting the XP system sit as an 'active' archive didn't ruffle any feathers.

However.. I had cause to switch it on a couple of days ago to try something out (FSX related) and walked into the MSE warning that my system wasn't protected.. click here to fix the problem. Clicking 'Here' takes you to Win8 upgrade. Well.. that was helpful 8) 'OK' I said to myself.. time to do something about this. I remembered one of the contributors here mentioning AVAST as an alternative so I found their site and downloaded the latest 'basic' version. I have to say that the basic version doesn't do much.. on a scale of 1-10 when compared with it's payware alternative, it scores a healthy 1!!! No matter.. the WinXP system isn't going to be doing a lot these days so basic cover is all I need. I have Malwarebytes Pro installed on it so that should cover a lot of what AVAST doesn't.

The install routine started and moved quickly to step 2 of 4. Step 2 of 4 seemed to be running for a hell of a long time during which I was being offered other 'must have' software. The 'Decline' button on this additional stuff appeared to be greyed out leaving no option but to accept.. if I wanted AVAST installed.. or so I thought. After the 3rd bit of software had been accepted.. a 4th was offered (note, the install was still on step 2 of 4) so I thought I'd try the greyed out looking Decline button. It worked!! Bu99er me :wall: Meanwhile, MWB was taking exception to these new progs (the 3 I'd unwittingly accepted) and it's Quarantine Folder was filling fast 8) Knowing now that the greyed out 'looking' Decline button was just a ruse, I hit a couple more until Step 2 of 4 moved to Step 3 of 4!! 8)

Eventually.. AVAST installed and updated then.. it started warning me that IE was unsecure and I should install Chrome. I declined the offer and ran an initial scan. It found a few things.. all but 2 of which had come down the line with these other 'must have' bits of software. The 2 that had been there for a while were known about and are the installer/cfg tool for the FSHeliCH Alouette2! Meanwhile.. MWB was telling me it had detected a shed load of stuff so I let that quarantine what it had found and ran another scan. After an hour.. all was peace and quiet. AVAST had shut up and MWB was happy nothing else was lurking.

I had cause to turn the XP machine on again today (it runs the printer which is networked) and I've lost another hour of my life. AVAST came up with a new box telling me that 3 bits of software (FlashPlayer, Firefox and WinRAR) were unsecure and needed updating. I let it run update for FlashPlayer (towit I had to dodge Chrome again) and after this had happened, it told me there was a new version of AVAST so I updated that. Thinking it was all over, an 'Almost Finished' page came up telling me to install Chrome. At this point, I gave up and installed Chrome. Having done that, MWB popped up and suggested I do another scan as it had detected unsavoury software so I let it scan and 3 files were found.. all of which are now in quarantine. Exhausted, I turned the XP machine off.. over an hour having elapsed and all this so I could print 2 rosters 8) In future.. I think I'll let it die.

ATB
DaveB B)smk

Re: M$ strikes again

Posted: 01 May 2014, 16:49
by Kevin Farnell
Are you sure that you downloaded Avast from the authentic website, Dave?
I moved over to Avast Free, a couple of months ago when a review in Computer Active magazine found it to be the best performing Free anti-virus (also beating some payware) over the previous 12 months.
I had none of the install problems that you encountered. However I do keep getting pop-ups ('nagware', I believe it's called) wanting me to upgrade to the paid for version.

Regards

Kevin

Re: M$ strikes again

Posted: 01 May 2014, 23:24
by GHD
I have just installed the IE fix for XP from the MS Update site.

Re: M$ strikes again

Posted: 01 May 2014, 23:51
by TSR2
That's pretty decent, I didn't think they'd do that to be honest. Cheers for the HU George :thumbsup:

Re: M$ strikes again

Posted: 02 May 2014, 00:03
by GHD
Yes, I was surprised since I no longer get notifications, but

Image

Re: M$ strikes again

Posted: 02 May 2014, 00:10
by DaveB
Yes Kevin.. it was from the AVAST site I pulled their AV. As for the 'nagware'.. it's no different from staying with IE8 and MSE to be honest. This cheesed me off as much as anything 8)

What does the IE8 security update update George?

ATB
DaveB B)smk

Re: M$ strikes again

Posted: 02 May 2014, 00:35
by GHD
DaveB wrote:What does the IE8 security update update George?
http://www.computerworld.com/s/article/ ... nerability