(Feb 11, 2022 08:30 AM)Dyne Wrote: They have been attempting to roll this out for years, Original plan was DEC 2019, then DEC 2020.
They have also tried virtualizing office which simply doesn't work for business PCs.
The death of macros has been taking its time, but we all knew it was coming. If they were smart they would also ruin .xll droppers while they're at it, but they won't for some years yet at this rate.
Good share.
.xll i think is harder for them to fix really. xll files is executable code from the beginning. Why they didnt crack down on macros before i wonder. But i guess in the end its all boils down to financial decisions and predictions. Noone gives a fk about the end user, only about the buttomline. If the analysis says no, then its no.
Fixing xll droppers seems equally as hard as fixing .exe or .dll droppers, they would need to change the entire format.
We are certainly moving towards more restricted use of code, and more restricted user enviroments. Again it all boils down to financial analytics. Do we want to sacfrifice ease of use for security. Not fully yet, but it is slowly moving that way.
I still dont understand why we live in a world where passwords are even a thing we use, and not some ancient shit you hear about on museum together with the telegraph
/E after reading the article, i really dont believe this will prove a significatnt security change for private end users. Most will, if they are convinced that what there is in document is interesting enough to enable it in the first place, will just skim through the new windows article, untill they find out how to enable the macro, and then run it anyway. It will be more a annoying thing for them, then something that stops malware.
If they clicked accept on the old system, they will also accept the new system. They where warned before too. They will just be annoyed at microsoft for having to spend 30 seconds on it instead of 1 haha