Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Perhaps I'll get Agile Bits take on this using their forums. I suspect they don't adopt a standard off-the-shelf security posture since it would likely be obsolete. Something like "hey, if someone has the credentials to access my naked photos and other documents, might as well let them have my passwords" is probably not the way they think about it.

I'll take our ex NCSC consultants from NCC Group over the vendor thanks.
 
Perhaps I'll get Agile Bits take on this using their forums. I suspect they don't adopt a standard off-the-shelf security posture since it would likely be obsolete. Something like "hey, if someone has the credentials to access my naked photos and other documents, might as well let them have my passwords" is probably not the way they think about it.

Agile Bits will quote standard security practices like any other vendor.

Apple should have a separate master password for Passwords and not default back to the account one, but if someone has access to your master password - by brute force or social engineering - it doesn't matter.
 
Starting with macOS Sequoia (v15), the same risk exists in 3rd-party password managers that have fingerprint biometric enabled, e.g., Dashlane. ...

Detail: on a Mac running macOS Sequoia, if Dashlane in Chrome has biometric unlock enabled, a fingerprint prompt appears when starting Dashlane in Chrome. If the fingerprint works, Dashlane opens, as expected. But if the fingerprint fails, a prompt appears for the Mac's password, not Dashlane's master password, as was the case before macOS Sequoia. I confirmed this with Dashlane tech support over numerous exchanges. They confirmed it started with macOS Sequoia.

Anyone with your Mac's user password can unlock Dashlane after the fingerprint fails. This is probably the same behavior in other macOS 3rd-party password managers, which would also rely on macOS to handle the fingerprint reader.

Per 1Password's documentation (https://support.1password.com/touch-id-mac/), and based on my experience with 1Password on Sonoma 14.7.2, the 1Password account password (formerly, called the "master password")--NOT the macOS user password--is required to unlock 1Password when Touch ID fails or if you just click the "Use Account Password..." button.

1736972487637.png


The 1Password documentation states:

Sometimes you’ll need to enter your account password instead of using Touch ID:

  • If the amount of time in Settings > Security > “Confirm my account password” has elapsed
  • If Touch ID isn’t available, like when the built-in display is closed on your Mac
  • If you add or delete a fingerprint from your device
I haven't personally verified the third bullet on Mac, but it works that way on iPhone/iPad.

That is not the case with 1Password. If biometrics fails you must use your 1Password password, not your macOS password.

@svenmany: Can you confirm 1Password biometric unlock works the same on Sequoia 15.2? (Maybe that's what you were saying, but I'm just trying to verify macOS 15 didn't actually break something.)
 
Agile Bits will quote standard security practices like any other vendor.

Apple should have a separate master password for Passwords and not default back to the account one, but if someone has access to your master password - by brute force or social engineering - it doesn't matter.

They might add a bit of perspective, but I agree that it will represent standard security practices.

There's a standard concept of data security risk levels. Some data is more sensitive than others. It's probably standard practice to provide additional restrictions on more sensitive data. The master password of 1Password is that additional restriction on the more sensitive password data.
 
  • Like
Reactions: Brian33
@svenmany: Can you confirm 1Password biometric unlock works the same on Sequoia 15.2? (Maybe that's what you were saying, but I'm just trying to verify macOS 15 didn't actually break something.)
Per 1Password's documentation (https://support.1password.com/touch-id-mac/), and based on my experience with 1Password on Sonoma 14.7.2, the 1Password account password (formerly, called the "master password")--NOT the macOS user password--is required to unlock 1Password when Touch ID fails or if you just click the "Use Account Password..." button.

This experience with Sonoma is the same that I experience on Sequoia 15.2. I haven't tried deleting a fingerprint, but I'm willing to test it if you want me to.
 
There's also the whole "all your eggs in one basket" issue. I still remember one evening last spring when I spontaneously got booted off of iCloud on every single Apple device I owned -- along with untold thousands of others. Apple of course never offered a peep of explanation.

I got lucky and was able to reset my iCloud password within like half an hour. But there were others on these very forums saying they were locked out for a week or more. If I'd had all my passwords and auth codes in iCloud, not hard to imagine some scenarios (travelling, for one) where I'd be totally f****ed.

So, I continue keep all my passwords in 1Password, and once a month or so I now do a full export to a file I keep on an encrypted disk image saved to multiple places. Seems paranoid, but the stakes are pretty high at this point.
 
I've had several repairs done by Apple on phones and the mac and the procedure is always the same:
They check you have backed up the device, disabled 'find my' and signed out of your Apple account so I don't see this as being an issue.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.