• 8 Posts
  • 1.2K Comments
Joined 1 year ago
Cake day: June 15th, 2023
  • lemmyvore@feddit.nltoPrivacy@lemmy.ml•[email protected]: An open source two factor auth app that syncs keys between devices?English
    10·
    5 hours ago

    Many people have a warped understanding of what “two factor” means.

    They conflate it with devices and they think it means that one of the factors (why one? which one? who knows) needs to be restricted to exactly one device.

    What “two factor” really means is that you should have more than one required factor of authentication so that if one is compromised the attackers still can’t get in.

    Ideally the factors should be spread across the “something you know” / “something you own” / “something you are” categories to complicate the manner in which they can be compromised.

    We can only reliably rememeber a limited amount of passwords, so like it or not we have to use some devices at least some of the time.

    The trouble with “something you own” is that it can be lost or damaged or stolen, and if you only have one of it then you’re fucked. So adding some redundancy is not a bad idea.

    The larger issue is that everybody is stuck into extremely rigid and outdated mindsets that date back decades. “Two factors” don’t have to be exactly two, and they don’t have to include exactly one password, and so on. It should be fine if you wanted to secure your account with 3 passwords, and should be up to you if one of those password is a barcode tattooed on your taint so you need a mirror and to bend upside down to scan it.

    Bottom line, use whatever you want and use your best judgment as to how secure is each factor. If you want to use something that syncs to multiple devices, go ahead. What you should consider is who has access to those devices and how it would affect you if they’re lost or stolen.

  • lemmyvore@feddit.nltoProgramming@programming.dev•Dev rejects CVE severity, makes his GitHub repo read-onlyEnglish
    6·
    5 hours ago

    This whole debacle is a festival of stupidity:

    • It’s a personal project that taxes the sole maintainer disproportionately.
    • Millions of idiots use it blindly and end up building elaborate software on it. https://xkcd.com/2347/
    • I’ll bet you 99.99% of those idiots use it only for ip.isPrivate(), which you can write yourself in 5 minutes.
    • The CVE is a non-issue (who the fuck would call a function that takes string notation with hex numbers?)
    • Appealing and reverting or downgrading CVEs is super complicated.

    At this point the maintainer is fucked no matter what they do, so archiving the project and telling everybody to fuck off right back was really the only sane thing to do.

  • lemmyvore@feddit.nltoSelfhosted@lemmy.world•Can you have local reverse proxies?English
    1·
    2 days ago

    If you mean to do that in the public DNS records please note that public records that point at private IPs are often filtered by ISP’s DNS servers because they can be used in web attacks.

    If you don’t use your ISP’s DNS as upstream, and the servers you use don’t do this filtering, and you don’t care about the attacks, carry on. But if you use multiple devices or have multiple users (with multiple devices each) eventually that domain will be blocked for some of them.