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

help-circle


  • One thing to consider. When the stocks that are part of a mutual fund drop… then your retirement contributions will be buying them on sale.

    Assuming the mutual funds are spread out to minimize risk (1 of the funds companies folds, etc) overall you’ll be better off long term.

    As you age you’ll start moving your investments to more stable options (talk to a financial adviser on the specifics for your plans). This way they that won’t benefit from huge gains but also are a lot less likely to be wiped out by massive drops.

    In the meantime look at how your funds are doing over time. Not even year to year but maybe every 2 or 3 years.



  • 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)












  • If a person is at the intro/intermediate level that advice may be sound enough. Since they’re less likely to apply proper rules to include those ranges of IP’s etc.

    Assuming it’s advising disabling it at the router/switch level and not just a per device level.

    Better would be to explain: Disable this until you’re familiar with the following concepts (see cited books/material for more info)