Skip to main content

Microsoft 365 Brings the Shutters Down On Legacy Protocols

2 months 4 weeks ago
Starting mid-July 2025, Microsoft 365 will begin blocking legacy authentication protocols like Remote PowerShell and FrontPage RPC to enhance security under its "Secure by Default" initiative. Admins must now grant explicit consent for third-party app access, which could disrupt workflows but aims to reduce unauthorized data exposure. The Register reports: First in line for the chop is legacy browser authentication to SharePoint and OneDrive using the Remote PowerShell (RPS) protocol. According to Microsoft, legacy authentication protocols like RPS "are vulnerable to brute-force and phishing attacks due to non-modern authentication." The upshot is that attempting to access OneDrive or SharePoint via a browser using legacy authentication will stop working. Also being blocked is the FrontPage Remote Procedure Call (RPC) protocol. Microsoft FrontPage was a web authoring tool that was discontinued almost two decades ago. However, the protocol for remote web authoring has lived on until now. Describing legacy protocols like RPC as "more susceptible to compromise," Microsoft will block them to prevent their use in Microsoft 365 clients. Finally, third-party apps will need administrator consent to access files and sites. Microsoft said: "Users allowing third-party apps to access file and site content can lead to overexposure of an organization's content. Requiring admins to consent to this access can help reduce overexposure." "While laudable, shifting consent to the administrator could disrupt some workflows," writes The Register's Richard Speed. "The Microsoft-managed App Consent Policies will be enabled, and users will be unable to consent to third-party applications accessing their files and sites by default. Need consent? A user will need to request an administrator to consent on their behalf."

Read more of this story at Slashdot.

BeauHD

SpaceX Starship Explodes On Test Stand

2 months 4 weeks ago
SpaceX's Starship exploded on its test stand in South Texas ahead of an engine test, marking the fourth loss of a Starship this year. "In three previous test flights, the vehicle came apart or detonated during its flight," notes the Washington Post. No injuries were reported but the incident highlights ongoing technical challenges as SpaceX races to prove Starship's readiness for deep-space travel. From the report: In a post on the social media site X, SpaceX said that the explosion on the test stand, which could be seen for miles, happened at about 11 p.m. Central time. For safety reasons, the company had cleared personnel from around the site, and "all personnel are safe and accounted for," it said. The company is "actively working to safe the test site and the immediate surrounding area in conjunction with local officials," the post continued. "There are no hazards to residents in surrounding communities, and we ask that individuals do not attempt to approach the area while safing operations continue." Starship comprises two stages -- the Super Heavy booster, which has 33 engines, and the Starship spacecraft itself, which has six. Before Wednesday's explosion, the spacecraft was standing alone on the test stand, and not mounted on top of the booster, when it blew up. The engines are test-fired on the Starship before it's mounted on the booster. SpaceX had been hoping to launch within the coming weeks had the engine test been successful. [...] In a post on X, Musk said that preliminary data pointed to a pressure vessel that failed at the top of the rocket. You can watch a recording of the explosion on YouTube. SpaceX called the incident a "rapid unscheduled disassembly," which caught the attention of Slashdot reader hambone142. In a story submitted to the Firehose, they commented: "I worked for a major computer company whose power supplies caught on fire. We were instructed to cease saying that and instead say the power supply underwent a 'thermal event.' Gotta love it."

Read more of this story at Slashdot.

BeauHD

American coders are most likely to use AI

2 months 4 weeks ago
Baseball, apple pie, and assisted programming

US-based software developers are the world's most prolific users of AI coding assistants, a trend that researchers believe has national economic implications.…

Thomas Claburn