personal-security-checklist VS zxcvbn

Compare personal-security-checklist vs zxcvbn and see what are their differences.

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
personal-security-checklist zxcvbn
55 59
15,249 14,595
- 1.3%
9.0 0.0
4 days ago about 1 month ago
TypeScript CoffeeScript
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

personal-security-checklist

Posts with mentions or reviews of personal-security-checklist. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-21.

zxcvbn

Posts with mentions or reviews of zxcvbn. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-17.
  • Show HN: A lightweight PHP library for checking password strength
    2 projects | news.ycombinator.com | 17 Jan 2024
    Lightweight is an understatement here.

    A client's project (with not necessarily technical customers) has had pretty reasonable success using the Dropbox originated library[1] for this, `zxcvbn`[2], on both frontend via js (for "instant" feedback) and on the backend via php (to enforce the requirements when writing password hashes to the database)

    1: https://dropbox.tech/security/zxcvbn-realistic-password-stre...

    2: https://github.com/dropbox/zxcvbn

  • How hard could it be? Sorting words alphabetically in Rust
    2 projects | /r/rust | 23 Mar 2023
    In contrast, let's consider the password "zxcvbn214". How might we assign an entropy to this password? Is it 369? Or 266 * 103? Anyone familiar with a QWERTY keyboard or Dropbox's password strength estimator knows that "zxcvbn" is hardly a random sequence of letters. This same principle applies to "l33t" speak, e.g. replacing all "e"s with 3s and "a"s with 4s. These strategies may "trick" simple entropy calculations into estimating a high entropy, but it won't trick sophisticated attackers. This leads to strength over-estimation, which is, I argue, the worst thing we can do in this context.
  • TIL There's Another YAML
    2 projects | news.ycombinator.com | 16 Feb 2023
    > except for ZXCVBN

    You mean the Low-Budget Password Strength Estimator?

    https://github.com/dropbox/zxcvbn

    Yeah, that name is totally legit.

  • Which tool can crack this password so fast?
    3 projects | /r/Bitwarden | 12 Feb 2023
    For any part of the password that the zxcvbn cannot match to a known pattern, it uses a brute-force cardinality of 10, i.e., it estimates that the number of guesses required to crack a password or password segment of length N is equal to 10N (equivalent to the number of guesses required to exhaust all possibilities if your password consisted only of numbers).
  • Bitwarden Design Flaw
    5 projects | news.ycombinator.com | 23 Jan 2023
    We took a similar approach to passphrase stretching in EnvKey[1] v1 (EnvKey is a secrets manager, not a passwords manager, but uses end-to-end encryption in a similar way). We used PBKDF2 with iterations set a bit higher than the currently recommended levels, as well as Dropbox's zxcvbn lib to try to identify and block weak passphrases.

    Ultimately, I think it's just not good enough. Even if you're updating iteration counts automatically (which is clearly not a safe assumption, and to be fair not something we did in EnvKey v1 either), and even with safeguards against weak passphrases, using human-generated passphrases as a single line of defense is just fundamentally weak.

    That's why in EnvKey v2, we switched to primarily using high entropy device-based keys--a lot like SSH private keys, except that on Mac and Windows the keys get stored in the OS keychain rather than in the file system. Also like SSH, a passphrases can optionally be added on top.

    The downside (or upside, depending how you look at it) is that new devices must be specifically granted access. You can't just log in and decrypt on a new device with only your passphrase. But the security is much stronger, and you also avoid all this song and dance around key stretching iterations.

    1 - https://github.com/envkey/envkey

    2 - https://github.com/dropbox/zxcvbn

  • What We Do in the /etc./Shadow – Cryptography with Passwords
    3 projects | news.ycombinator.com | 6 Jan 2023
    > There's another end of all this that I also never see addressed in writeups like this one: lots of users are still really bad at passwords.

    Author here.

    I was originally planning to write a blog post about my experience reporting cryptography-related bugs to password managers in 2022. (I had findings for LastPass, 1Password, and Keeper.)

    My experience with LastPass was abysmal. I wrote a thread about it here: https://furry.engineer/@soatok/109560736140669727

    However, I found in my early draft that I spent a lot of time explaining these algorithms, so I decided to spin it off into a separate article. Thus, this post was conceived!

    > Readers capable of implementing something like OPAQUE will already have a pretty good handle on most of what's written here. All other developers will just grab whatever "the" off-the-shelf solution is for their language and tech stack, and any recommendations for those are conspicuously absent here. What are the best resources for the most popular tech stacks currently? PHP introduced the password_hash() function (and related functions) in its standard library a while back. It defaults to bcrypt, and most php devs should probably just use those functions, unless they're sure they know better.

    I tried to make the post a good balance of fun and informative, but the audience was "people who want to know more about cryptography with passwords" not specifically developers.

    As you indicated, if you're developing something, the password_hash() / password_verify() API your language provides is likely 1000x safer than rolling your own anything. If there is to be improvements in the cryptography for a given programming language, it should be an update to whatever the de facto standard library is for that language.

    PHP has the password extension built-in. Python has passlib. Node has the crypto module. Etc.

    > For a while, some misguided sites tried to prevent people from pasting passwords into their login forms. I have never seen the inverse: a site that prevents users from typing a password. Is there a reason that wouldn't work?

    I'm not confident in this, since it's 4:46 AM for me and I should probably be sleeping instead of reading HN comments, but isn't this exactly how Passkey is supposed to work?

    Anyway, thanks for your insightful feedback. I already planned a teardown into the reverse-engineered internals of popular password managers and my experiences with them. Because of your comment, I might also make a future blog post targeting developers.

    In the meantime, here's some cool stuff:

    https://github.com/dropbox/zxcvbn - A reasonable approach to password strength estimation (although I think their calculation needs updating in 2023)

    https://github.com/DivineOmega/password_exposed - Checks if a given password has been exposed in a previous breach (uses the HIBP hash database)

  • Password Strength Recommendations for 2023?
    2 projects | /r/cybersecurity | 27 Dec 2022
    Did you hear about that one? https://github.com/dropbox/zxcvbn
  • Password Requirements: Myths and Madness
    2 projects | news.ycombinator.com | 22 Dec 2022
    The author links to a recommended library in the blog post

    https://github.com/dropbox/zxcvbn

  • I made my first program, a password generator.
    3 projects | /r/Python | 19 Nov 2022
    See also zxcvbn and original for the rationale.
  • This collecting personal data?
    2 projects | /r/Database | 18 Oct 2022

What are some alternatives?

When comparing personal-security-checklist and zxcvbn you can also consider the following projects:

awesome-cybersecurity-blueteam - :computer:🛡️ A curated collection of awesome resources, tools, and other shiny things for cybersecurity blue teams.

SecLists - SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

monkeytype - The most customizable typing website with a minimalistic design and a ton of features. Test yourself in various modes, track your progress and improve your speed.

keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.

Filterlist-for-AdGuard-or-PiHole - A very aggressive filter-list that consolidates over 370 lists for use in AdGuard Home, Pi-Hole or similar.

privacyguides.org - Protect your data against global mass surveillance programs.

awesome-bugbounty-tools - A curated list of various bug bounty tools

dumb-password-rules - A compilation of sites with dumb password rules.

Next.js - The React Framework

Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.

React - The library for web and native user interfaces.

serve - Static file serving and directory listing