I will burn your servers to the ground, foul villain
I will burn your servers to the ground, foul villain
FWIW: these types of password rules are discouraged by NIST -
Many companies ask their users to reset their passwords every few months, thinking that any unauthorized person who obtained a user’s password will soon be locked out. However, frequent password changes can actually make security worse.
It’s difficult enough to remember one good password a year. And since users often have numerous passwords to remember already, they often resort to changing their passwords in predictable patterns, such as adding a single character to the end of their last password or replacing a letter with a symbol that looks like it (such as $ instead of S).
So if an attacker already knows a user’s previous password, it won’t be difficult to crack the new one. The NIST guidelines state that periodic password-change requirements should be removed for this reason.
2FA: two factor authentication. So using a password (something you know) in combination with something else, like something you are (buometrics) or something you have (security token, phone with authenticator app)
OTP: One-time password. A password you can only use once. Can be a list of passwords where you have to use the next one on the list with each login or any other mechanism that provides a unique password for each login.
TOTP: Time-based one time password. An OTP scheme where the password is derived from a shared secret and the current time. Like Google Authenticator.
FIDO2: Fast IDentity Online version 2. A standard that lets you use an authentication device to log into online services. This can be in the form of a USB key or something built into your computer (e.g. on a Mac you can use the built-in fingerprint scanner).
2FA - Two factor authentication, you get asked a second secret besides your password.
OTP - one time password, you receive a code over SMS or mail.
TOTP - Time based one time password, you have to have an authentication app that creates a clock based cryptographic code.
FIDO2 - fast identity online standard version 2, is a set of ID verification. Usually you’re asked to confirm access on another certified device. Like google asking you to check your phone for a notification when logging into a new browser.
The attack vector is as follows:
The various physical dongles prevent this by using the asking domain as part of the hash. If you activated the dongle on Evil.com, it’ll do nothing on Good.com (except hopefully alerting the SOC at Good.com about a compromised username and password pair).
that would instantly make me very dumb and require a lot of explaining on the phone. like “when I say hello mister Thompson and press down on your foot then you smile and nod, do you understand?” levels of dumb.
“I’ve used up all the vowels! there are only 5! this means the only password left is rhythm”
“no you can use the same vowels just they can’t be in the same place”
“like I have to do it in my kitchen?”
“no the same place in the word”
“so it has to be the same word with different letters?”
“no, it has to be a different word with different letters”
“well like I said I already used all the vowels”
Ah, crap.
www.ibm.com/docs/en/i/7.1?topic=passwords-passwor…
Those are some aggressive password rule options.
On the plus side, it may be over engineered all of the way to fuck and back. (Or not)
I use a memorized passphrase with a random string stored on a mooltipass or onlykey. I use both interchangeably for vendor diversity.
They are both pin protected and act as USB keyboards (how I use them). They have more features like FIDO2 (both), WebAuthN (moolti), Bluetooth (moolti), etc.
I only store my computer decryption and account password plus my bitwarden password on them (random part for use with memorized passphrase). After that I just use bitwarden once I’m logged in.
I was a happy OnlyKey customer until I wanted some spares a couple months ago and they were out of stock. That’s when I got a Mooltipass. The OnlyKeys are back in stock this month so I did get some more as backups.
OnlyKey is lower tech which I honestly think makes it more reliable. It also supports a longer pin.
Mooltipass input is the scroll wheel which you push to click. Pin is only 4 digits but supports all hex characters where OnlyKey is only 1-6.
Passwords are stored on device with the OnlyKey. With the Mooltipass its on a card you can swap out, clone, etc.
OnlyKey is powered through USB. Mooltipass has a battery. Battery needs to be cycled often so I use it as my daily driver for that reason. I’d probably use the OnlyKey if it were not for that. I feel it is faster for my workflow since I can pick 1 of 12 passwords in one short or long press on the device. Mooltipass I have to go through a couple menus and confirmations.
I can see the attraction to the additional features of the Mooltipass but I just don’t use them (at least yet).
Either are great though. The extra input requirements of the Mooltipass are not that bothersome.
Ordered an Only Key - they’re on sale, which is nice, but I think for my use case it’s easier, as well.
Thanks a ton!
Great to hear! They are awesome for system access before a password manager is available.
Looking to play with the fido2 function soon to unlock luks encrypted partitions for my headless media server after a power outage.
just make the password manager super secure
Remember when everyone said LastPass was that manager?
Yes yes but I don’t mean when I’m told to change one. I mean when I’m trying to login as usual, password doesn’t work, so I change it. Just to test of the password I was using was wrong, that’s what I use first- and it’s rejected.
I remember Epic would do this on a DAILY basis at some point last year. It was so irritating. “Ah yes the brand new password from yesterday that worked yesterday but that we didn’t recognise on the login page today? Well we do recognise here on the reset, jokes on you!”
There could be many reasons they don’t prompt you to change: they meant to send an email but your notification preferences disallowed it, they sent an email and you missed it, they wanted to keep it quiet, they forgot to add the message and ux flow to change password, or they’re incompetent and didn’t know they needed to do that.
The Epic thing I’ve never seen before but that’s definitely incompetence and/or a very weird edge case bug that just slipped past them.