this post was submitted on 25 Oct 2023
96 points (99.0% liked)
Technology
37754 readers
298 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
But a workaround is. Configure your password manager (or switch to another password manager) so it doesn't automatically fill usernames and passwords as soon as you open a webpage. Set it to fill the credentials when you click a button or hit a hotkey.
And after this security flaw is fixed? Leave the settings like that. Because this isn't the first time autofil has resulted in a major compromise and it won't be the last time either.
PS: this speculative execution bug was reported to Apple a very long time ago and there are experimental settings you can change to test the fix... but they might be buggy. Modifying your password manager's behaviour will not be buggy. The setting is:
defaults write com.apple.safari InternalDebugProcessSwapOnCrossSiteWindowOpenEnabled 1