• 0 Posts
  • 307 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle






  • The hassle and delay is part of how it works. If there was a seamless catch all then it wouldn’t be feasible to make it secure.

    Having a second physical factor, as much as it can be a hassle, is much better than any single factor.

    Your password can be breached, brute forced, bypassed if there’s an issue somewhere.

    Your biometrics can’t be changed so anything that breaks them (such as the breach of finger prints in databases, etc) makes them moot.

    A single physical token can be stolen and/or potentially cloned by some attack in physical proximity (or breach of an upstream certificate authority)

    But doing multiple of those at the same time. That’s inordinately much harder to do.

    I will say the point/gist of the article is a good one. The variety of types some used here and others used there does make it a hassle to try to wrangle all the various accounts/logins. Especially in their corporate and managed deployment which isn’t saving passwords and has a explicit expiration of credential cache (all good things)












  • While I can’t speak to specific apps alot of times it’s house cleaning stuff.

    Maybe some bug that affects a certain number of users is found and fixed. And the update resolves that bit, since you weren’t affect, you don’t notice it.

    Other times it’s to include fixes in libraries they’re using. So, for example, a JSON parsing library may have a security fix and they updated their app to use that newer version.

    Another could be some behind the scenes api/library updates. Maybe a service they’re using for content (such as interacting with Lemmy) or maps or advertisements is being updated and they need to point their app to the new service address or change how they interact with it.

    And of course there could be feature updates but those, usually, would be things you’d notice. Although, in some cases, it may be packaged with the application but waiting for some criteria (a backend service to be ready) or may even be part of A/B testing where some users get one change while others don’t so the developer can see which features are preferred using real data.