
"Secure by Default"
See icon... ----------------------------------------------------------------------------------->
Microsoft has warned administrators that legacy authentication protocols will be blocked by default from July, meaning that anyone who hasn't made preparations already could be in for a busy summer. The notification in the Microsoft 365 Message Center this week – MC1097272 – warned that the default settings in Microsoft 365 …
1. What sort of Queen's English-destroying, euphemistic, pea-brained cockwomble writes "non-modern" instead of "old" or "older"? (Hint: the same sort which writes "experience" instead of "program", or "surface" instead of "display" or "exhibit".)
2. This is just security theatre designed to make you think Microsoft "cares" about good security. Yes, it's good that they're closing these holes, yet based on decades of history, MS will continue their malpattern of creating new protocols with inherent vulnerabilities, vulnerable implementations, and/or bad defaults.
You write this: 1. What sort of Queen's English-destroying, euphemistic, pea-brained cockwomble writes "non-modern" instead of "old" or "older"? (Hint: the same sort which writes "experience" instead of "program", or "surface" instead of "display" or "exhibit".) and then use the made up word malpattern.
Bravo!
The mention of FrontPage brings back memories. I was using it over 20 years ago to manage the website of a search and rescue charity. It worked well via dial-up internet (which is what I had) by sitting entirely on my own PC with a sync'd copy on the public server. Each time I had changes to make, I could do them locally, then hit a button to dial up and sync. The editor itself was a dream; not necessarily as versatile as others, in that you used its proprietary formats, but easy to produce something presentable. Considering a lot of those accessing it wouldn't have the latest browsers, nor fast links, it actually forced me to have a site that was usable by those who needed it - rather than, as happens with many sites today, forces a load of unnecessary (for them) crud onto users. It also managed all the page links in a simple graphic, so moving links around to ensure the most relevant at the time were more easily reached was a breeze. For example, if the SAR team were on a flood rescue, I could move the site focus onto flooding issues; if they were attending the aftermath of an earthquake then the site focus would be on that.
FP wasn't popular with the tech writers as it didn't follow the latest web/HTML standards - standards that may have given developers more control and MS replaced FrontPage with something that did what every other editor at the time did, dropping the features that I found most useful.
It took a random article in a magazine (remember those?) for me to find out only today that as well as Win 10, M$'s protocols bonfire is taking file types for the old Word and Excel (and presumably PowerPoint and Access?) and junking them, about the same month as W10 EOL.
Ok, anything still using those file types is old, possibly (though I'd hesitate to say "probably") not needed again, or is in current use and can easily be saved as a .***x file (or e.g. .xlsm with macro). Not nearly as well known about as W10 EOL, but people need to assess and if necessary convert. Also stop updates to older Office programs (2010, 2013, 2016 etc) so M$ can't deprecate your old files beneath the radar. Go to settings and remove updates to applications.
And there are millions (I mean that) of historical documents in the old formats on obscure, and less obscure, web sites. Not to mention .ppt. These formats will never, ever go away. Thank heavens for LibreOffice, indeed. I haven't bothered with the MS apps for at least ten years.
>M$'s protocols bonfire is taking file types for the old Word and Excel (and presumably PowerPoint and Access?) and junking them, about the same month as W10 EOL.
I can't find any citation for this. I think it's incorrect. Some older apps are being EOL'd but what you allege is not mentioned anywhere.
Whether this particular instance is true or not, (.doc/.xls files) this type of action from Microsoft emulates the actions of a certain "1930s Chancellor" burning the books. Without access to legacy formats, history is being disposed of, which is probably what some (esp MAGAtypes of Truth Scandal persuasion), would like.