axelson
Scenic Core Team
Hi, I’d like to present PasswordValidator, a simple easy-to-use enforcer of common corporate-style password rules such as length and character set (i.e. number of minimum characters to use of each class) as well as implementing custom validation rules.
Of course if you can convince the business side of your company to not require specific rules, but instead allow a longer minimum length if the rules are not met that would be better than restrictive character set rules.
Links:
Trending in Announcing
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
I needed to reuse React components from my Chrome extension in my Phoenix/LiveView backend. I noticed that for Svelte/Vue, there are live...
New
I released Doggo, a collection of unstyled Phoenix components.
https://github.com/woylie/doggo
Features
Unstyled Phoenix components....
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hello
Published a new library - ProcessHub!
ProcessHub is a library designed to manage process distribution within the Elixir cluster. ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
It’s not that it’s vocabulary is too advanced. It’s something worse.
I get lost trying to follow even a paragraph written by Claude. It’...
New
This showed up on my feed.. anyone heard of it? Just hype?
Ox Alpha is a reasoning model designed for coding, sustained ag...
New
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Have you thought about supporting a NIST mode to have it follow the NIST Federal Password Guidelines (Section 5.1)? This seems to be pretty standard in areas that I’ve worked as the password requirements. In general it just has a minimum length of 8, a minimum maximum length of 64, any ASCII printable character must be allowed and any unicode character ‘should’ be allowed, pasting should be allowed, a blacklist of compromised values is allowed and it is allowed to block often-guessed patterns such as dictionary words and so forth, more importantly it has this sentence:
No other complexity requirements for memorized secrets SHOULD be imposed.A library that verifies according to the NIST standards with a lot of configureable optional sets would be very nice.
axelson
Thanks, that seems like a reasonable consideration. Perhaps it could be implemented kind of like a preset. I added an issue to track it: Support NIST 5.1 requirements · Issue #4 · axelson/password-validator · GitHub