for anyone still reading:
in july, we told sparkfun they needed to get their house in order. for years, sparkfun's leadership ignored specific behavior from leadership (and employees, now former... they had created and promoted hate sites, photoshopped images, and harassment targeting limor, me, and others at adafruit. this was done on company time, shared, promoted. this was reported to them. it was documented and ignored. that was the big issue i wanted them to get some hr training on, or _something_
months later in 2025, the same individual resurfaced and re-promoted it with what appears to be nate's blessing at the time. we again told sparkfun to deal with this. instead of addressing the behavior, sparkfun’s response was to “ban” adafruit from purchasing teensy by invoking a vague, secret set of rules that neither we nor paul (the creator of teensy) were allowed to see.
this is not a one-off. nate (the founder of sparkfun) has done this before. anyone who has worked with him long enough knows this is how conflict is handled: deflect, escalate, and try to punish rather than deal with the underlying conduct.
we do not respond to bullying by backing down. we never have. that is why we are here.
To confirm a user supplied password matches you run input into the same hash function again with the salt+pepper and compare it to the value in the database.
That way if the database is stolen, the attacker cannot recover the contents of the passwords without brute forcing them. Encrypting passwords is not recommended because too often attackers are able to recover the encryption keys during the same attack where the password data is extracted.
[0] https://en.wikipedia.org/wiki/Bcrypt
[1] https://en.wikipedia.org/wiki/Scrypt
[2] https://en.wikipedia.org/wiki/PBKDF2
[3] https://en.wikipedia.org/wiki/Salt_(cryptography)
[4] https://en.wikipedia.org/wiki/Pepper_(cryptography)