Microsoft Extends EMET End of Life Date (itnews.com.au)
An anonymous reader writes: Microsoft will continue to support and provide security patches for its Enhanced Mitigation Experience Toolkit security software for Windows until July 31 2018, after taking customer feedback into account. EMET is a security utility software popular with enterprise customers running supported versions of Windows. It uses mitigation techniques to block attackers from exploiting vulnerabilities in software. The company's lead program manager for operating system security, Jeffrey Sutherland, said while EMET 5.5x will continue to be supported for another 18 months after the original end of life date of January next year, Microsoft recommended customers migrate to Windows 10 for improved security.
Ta-da!
EMET is a security utility software
No, it's not. It's a program, or a software suite, etc. There's no such thing as "a software".
"Enhanced Mitigation Experience" ?
Have to hand it to the marketing guys, computer security is a "mitigation" "experience" that Microsoft has "enhanced."
EMET doesn't block malware from exploiting vulnerabilities, it tries to prevent malware from doing any damage after it gets through. If so, that's not at all unreasonable. You can't ever block all possible holes; at best, you can block the ones you know about, but you can add an extra layer of protection to the programs and files that malware targets. If so, that even gives you a little bit of protection against zero day exploits, because it doesn't do crackers any good to get in if they can't steal or corrupt your data.
Good, inexpensive web hosting
How about listening to users and extending Windows 7 support even longer, and perhaps un-crippling the Windows Update service on that platform?
Windows 7 gained more new users than Windows 10 in last two months
you mean your marketing people said it would be good PR move to keep it around in light of all the hacks and breakins even though the product itself is nearly worthless, it's still good PR.
if microsoft actually took "customer feedback into account"... they never would have released vista, or 8, or 10; xp and 7 each would have had TWENTY year lifespans, as would office 97 and 2010.
AND.. there would be..
no telemetry/spying bullshit; no forced or "highly encouraged" push to online accounts or cloud services, no such thing as software 'activation', no forced windows/office updates (all user configurable like the good old days), internet explorer never would have existed... etc etc etc.
Just more bandaids that don't fix the problem.
A "mitigation" is something done until the bug is FIXED.
Not something that should be permanent. That just means the BUG is still there.
Perhaps they are relying more on Defender in the future? Why would such announcement be made, unless the EMET 6.x ceases to be compatible with earlier Windows version or the EMET product is discontinued, or the functionality integrated into Defender? Compatibility issues alone make integration of the present EMET directly into Windows a really difficult proposition.
Just another EMETic product from Microsoft. They excel at that.
bring it back from the dead. you continue to ship it alone and within the free offering of SysInternals Suite. Development ceased years ago, yet you still distribute it! please bring back development of this important tool!
Is it the word you write on the forehead of a golem to make it come alive?
If you use EMET's built in protection functions, lots of software, Microsoft applications even, stop working.
It's a horribly designed POS.
Stack smashing protection in the CPU itself (not overwriteable iirc) vs. Return Oriented Programming "fishing around" to defeat ASRL protections I noted https://news.slashdot.org/comm... that I read about a while back...
ASRL is only a "delaying action" @ best when they chain a few asm 'hunters' together & start testing for where in memory a program or OS using it is placing call stacks 'randomly'.
Software protections FAIL here eventually due to said "fishing". Hardware mirrors won't & imo will be READ ONLY to software.
I heard tell INTEL has "CET" ready to build to do this in their next-gen CPU's & good for them - put those out already!
* Imo, that'd work & be a great layer of protection in the CPU itself (vs. software protections) via "shadow stacks"... & iirc, it's NOT implemented in CPUs yet. It should be.
APK
P.S.=> It'd stop TONS of "buffer overflow" type exploits as well as overriding function call tables in memory (which reminds me in a way of overriding jump tables which 'old-school' .exe infection viruses did) etc.... apk