Several programs use the term “Autofill,” although as mentioned in the Strongbox documentation shown below, there is an “Apple Password AutoFill subsystem.” This subsystem is used in most(all?) iOS browsers and only for Safari on macOS. At a minimum, Codebook, mSecure, Minimalist, and Strongbox take advantage of this on the Mac.
Strongbox documentation:
https://strongbox.reamaze.com/articles/how-to-autofill-on-macos?q=
AutoFill Passwords in Safari on Mac
With the release of MacOS Big Sur Apple now provides a fully integrated way to fill in your passwords on different sites and App, all inside that App or site. There’s no need to switch to your Password Manager and Copy/Paste. Strongbox (as of 1.14.0) now integrates with Apple’s Password AutoFill subsystem to offer suggestions and fill in passwords. This follows on from the iOS integration which has been available for a few years now and has proven very convenient. Finally it has come to Mac.
NB: Mac AutoFill support is only available with Strongbox Pro. You can try this out for free for 3 months with no obligation to buy. We hope you’ll love it.
Note that this AutoFill system on works on Apple’s latest OS (MacOS Big Sur) and only with Apps and Browsers that have upgraded to support the Password AutoFill system. So far, as of post time, the only major browser that supports AutoFill is Safari. We believe this will change over the coming months and we should see ubiquitous Password AutoFill support in most browsers and Apps in short order.
Strongbox documentation:
https://strongbox.reamaze.com/kb/se...re-secure-than-using-plugins-or-the-clipboard
Is Apple’s Password AutoFill More Secure Than Using Plugins or the Clipboard?
We believe using the built in Password AutoFill subsystem is the most secure way to fill your passwords, and should become the de facto method for all browsers, apps and password managers in the future.
Of course, as with everything the devil is in the details. In principle, Apple's Password AutoFill is absolutely a better model, a system fully designed for the transmission of sensitive credentials from a Password Manager to a requesting 3rd party App/Browser. There's no globally shared data that can be sniffed, so it's a thousand times better than using clipboard. It's also doesn't require a plugin and some arbitrarily designed IPC process. Further because the browsers do the integration work, it provides a unified standard for websites to fit into, and so, eventually, no more un-fillable logins. Having a single standard is beneficial.
The only issues we can see is if the 3rd party app/browser implementation (Safari, Chrome, Firefox etc), the receiving App that is, has some kind of security issue, but then this is always the case, even with other methods. Therefore, even in the worst case scenario, we believe using the system provided Password AutoFill subsystem is at least as secure as other methods, and probably more secure. This also leaves out other non security based factors like improved UX, simplification for websites by having a common standard.
In all, we're betting on Password AutoFill on Apple platforms.
What about Chrome and Firefox on MacOS?
Unfortunately Chrome and Firefox are slow off the mark here in integrating with Apple Password AutoFill on MacOS. One of the best things we can do is pressure Chrome/Firefox... Please add your voice below!
Chrome
bugs.chromium.org
Firefox
NEW (nobody) in Toolkit - Password Manager. Last updated 2024-09-18.
bugzilla.mozilla.org
May 16, 2023