News for hackers. Stuff that matters.
Re:Finding Pwned Passwords with 1Password by grinsekatze on Friday February 23, 2018 @10:06AM (#16446685)
I still don’t get why someone using a password manager would make up passwords themselves instead of randomly generating long and strong passwords...

The way they implemented this is nice, but seems a bit pointless to me.

Re:Finding Pwned Passwords with 1Password by whichdan on Friday February 23, 2018 @10:12AM (#16446728)
Lots of people may have recently switched to a password manager, and now use it to store old passwords that they haven't regenerated. It's very likely a common use case.
Re:Finding Pwned Passwords with 1Password by r3bl on Friday February 23, 2018 @10:34AM (#16446909)
Heck, you don't even to switch to it recently!

I've imported my passwords from Firefox's password manager to a dedicated one a few years back, and I've been generating new passwords ever since.

There's still dozens of occurrences of the one-password-for-all-services I've used previously, because nobody will go through the hassle of changing passwords in hundreds of online services. I do change it whenever the autofill appears too short to be randomly generated, but I still didn't get rid of all of them.

With that said, I'm not using 1Password and I've already checked my old password in Troy's service to make sure it wasn't in a breach.

Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @11:12AM (#16447187)
Password rotation is a major issue.

If we'd use something like certificate auth it'd be less of an issue, but currently password managers are a horrible trend because they encourage using your password for a service for kany years. Ideally you'd rotate them every 60 days. Automating that is hell.

It'd be much nicer if we could just use OIDC with user-configurable endpoint.

Re:Finding Pwned Passwords with 1Password by jedberg on Friday February 23, 2018 @12:49PM (#16447931)
Password rotation has been shown time and again to be worse than just using a unique strong password.

With rotation, there is a tendency to just use the same password but increment a digit at the end, or to write them down because people forget them. A password manager helps with this, but if you're using a password manager, then you can use a different password everywhere.

Password rotation was recommended in the days when people used the same password everywhere and had to memorize them because password managers weren't a thing.

Password rotation gains you nothing if you're already using strong, unique passwords. The best it will gain you is preventing your account from being accessed if they have already breached the password file, cracked it, and come back after the rotation period. But at that point they've already had access to the system and your password is meaningless anyway, so you didn't actually gain anything.

Re:Finding Pwned Passwords with 1Password by jmulho on Friday February 23, 2018 @02:18PM (#16448593)
> "...if they have already breached the password file, cracked it, and come back after the rotation period..."

Suppose it will take 100 years to crack your strong unique password once the file is breached. If the rotation period is 90 days, rotation gains you something. Suppose they got the password file from a database backup. Your password isn't meaningless yet. You'll be fine as long as you rotate it within the next 100 years.

Re:Finding Pwned Passwords with 1Password by dsacco on Friday February 23, 2018 @11:40PM (#16451704)
> Suppose it will take 100 years to crack your strong unique password once the file is breached. If the rotation period is 90 days, rotation gains you something.

A strong password takes billions of years to crack with current computing power, assuming an entire datacenter is coordinating offline cracking on your password in particular.

Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @02:40PM (#16448760)
Unless the hackers simply modify the service itself, and log every password a user inputs to their server.

And tada, they got your password.

Re:Finding Pwned Passwords with 1Password by ribosometronome on Friday February 23, 2018 @04:52PM (#16449952)
If the hackers have compromised the service to the point they are able to manipulate the service unnoticed, isn't the horse already a little out of the barn?
Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @08:13PM (#16451031)
Sure, but this is a common issue, and hackers getting full control over servers is a common issue and the source of many credit card leaks.
Re:Finding Pwned Passwords with 1Password by dsacco on Friday February 23, 2018 @11:41PM (#16451706)
Yes but...password rotation doesn’t defend against that case either...so it’s irrelevant.
Re:Finding Pwned Passwords with 1Password by kuschku on Saturday February 24, 2018 @06:20AM (#16452791)
Rotating credentials prevents them from being used for a longer time after they've been stolen.

This is the sole reason why Let's Encrypt does 30-day certificates, and why the session tokens in OIDC are usually a few minutes at most.

The only one that's using a session token without invalidation time, forever, is Uber, and that was heavily criticized last time on HN.

And now, everyone's apparently in support of using the same password as login token for decades, never changing it.

Re:Finding Pwned Passwords with 1Password by dsacco on Saturday February 24, 2018 @09:08AM (#16453287)
You’re jumping all over the place.

Passwords != session tokens != certificates.

Passwords are a form of access control. I repeat: a strong password cannot be brute forced for billions of years. Even with technological advancements, most strong passwords are well over what’s required to literally be safe for a lifetime.

Certificates are not a form of access control, like I explained in my other response to you. They are a form of cryptographic authentication. Digital signatures cannot be revoked offline, which is a problem because they’re used by other parties for validating trust. Therefore, certificates have a built-in dead man’s switch that requires renewal.

Passwords are not used for validating trust. They’re not comparable to certificates. Stop using certificates as an example of why passwords need to be rotated, because certificates don’t even use “rotation” in that sense of the word.

Re:Finding Pwned Passwords with 1Password by kuschku on Sunday February 25, 2018 @10:13AM (#16459304)
> Passwords are a form of access control. I repeat: a strong password cannot be brute forced for billions of years. Even with technological advancements, most strong passwords are well over what’s required to literally be safe for a lifetime.

The topic was never about brute forcing, that’s irrelevant.

It’s always about exfiltrated passwords, certificates or session tokens.

You usually have additional authentication requirements so that changing the password requires more than just the password, but an attacker that exfiltrates the password can still read everything.

For example, an attacker that obtains my onlinebanking password will be able to read all transactions, but not make changes. In this way, the password acts identical to a session token – an attacker exfiltrating a session token will get the same access.

The goal is to reduce this ability – changing the password as often as the offline session token ensures that if an attacker had such read access, as is possible with many services, this access will not continue forever.

With your suggestion, of using an identical password for decades, a potential attacker has for decades read access to the bank account. This is undesirable.

Yes, preventing exfiltration would be better, but exfiltrating session tokens and passwords is identical in terms of attack surface, and as result, they should be protected identically.

Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @01:02PM (#16448007)
I'm talking about automated password rotation. A new 128 byte random base64 password every month.

Rotating credentials is important, even if you automate them. For the same reason that Let's Encrypt only provides certificates with 90 days validity, and that OAuth2 Offline tokens are usually limited to 90 or 180 days.

Ideally we'd use OAuth2 for everything, as that'd allow proper usage off offline tokens that allow the client to generate short lived session tokens, but we don't, instead we're using passwords everywhere, and we'd ideally want to have the same validity there.

The optimum would even be using challenge response authentications, or client side certificates.

This isn't a comparison of manual password management to password managers, but a criticism of password managers when compared to 30-day rotation cycle of client-side certificates.

Re:Finding Pwned Passwords with 1Password by eridius on Friday February 23, 2018 @01:31PM (#16448235)
Rotating passwords is only important if the site has been compromised (or you've been compromised, such as being phished). For the former, 1Password already has the Watchtower functionality where it tells you if a site is known to have been compromised since your password was generated, and for the latter, well, if you're being phished then you'll probably figure it out pretty quickly when the attacker steals your account.

In any case, if you really want to rotate passwords, 1Password has a "Security Audit" section with sections for "3+ years old", "1-3 years old", and "6-12 months old" passwords (and duplicate passwords, and weak passwords, and watchtower alerts), so you can rotate if you want to.

Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @01:41PM (#16448315)
Rotating credentials is also important as an additional layer of security to prevent misuse.

Sadly, currently this all is highly theoretical. The first thing we should focus on is getting 2FA (TOTP/HOTP or U2F) authenticated login on every service that doesn’t use OIDC. Even this very site, HN, has no such functionality (@dang, @pg: Why?)

This is a much more important first step, and once that’s fixed, we can look at improving credential rotation, and providing global SSO with browser credentials.

Re:Finding Pwned Passwords with 1Password by eridius on Friday February 23, 2018 @01:47PM (#16448356)
I'd wager HN doesn't have 2FA because there's not much damage you could do if you compromised someone's HN account. At best you can pretend to be someone else for a bit, but in most cases that's harmless. There's only a handful of accounts I can think of where it would be problematic if someone started impersonating them.
Re:Finding Pwned Passwords with 1Password by always_good on Friday February 23, 2018 @02:22PM (#16448620)
I work in online gambling and 2FA is a feature everyone says they want but doesn't use because it's annoying. Just query the amount of users actually using 2FA on your site if you've set it up. Now compare it to the number of people who said that they can't take your site seriously until you have it.

I'm not saying 2FA is bad, but these people like the person above lives in a hilarious bubble if they think a website like HN is missing out by not having it.

It comes off as concern-masturbation, if I may be so vulgar.

By the way, the best thing we did for security across our gambling network is to generate passwords for users. Nobody uses 2FA, and the people that use it aren't the ones that need help. But everyone reuses passwords.

Re:Finding Pwned Passwords with 1Password by odammit on Friday February 23, 2018 @05:26PM (#16450166)
Kinda agree about it being annoying.

I think MFA is important and have it enabled for every service that offers it, but we have MFA set up for our CLI access to AWS and I used to let out a volume of curses frequently when my token expired.

I eventually ended up adding a bash alias “damn”[0] that pipes my current MFA token into the AWS CLI so whenever it expires I can just type “damn” and be logged back in.

I like the magic link approach Slack and Medium use - although I have frequently cursed the inconvenience of having to log into gmail.

[0] why damn? Fuck was taken: https://github.com/nvbn/thefuck

Re:Finding Pwned Passwords with 1Password by spondyl on Friday February 23, 2018 @04:11PM (#16449657)
As someone who uses a Yubikey for physical 2FA, I happily use it for things like my email and Github but then I just click trust the device for X days because, yeah, it can be a pain every time.

I'm moving to KeepassXC currently and if you use a Yubikey challenge, you (by default) have to press it anytime you save or update a record which is a big pain. I think you can change it but I worry it might crash (I'm running unstable for the browser extension) or I might forget to save

Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @04:31PM (#16449802)
Personally, I use Yubikey or TOTP (with RedHat’s FreeOTP) for everything.

But that can only work if most services you’re using are using SSO, and you rarely need to reauth. I need to reauth every time I log in, every time I want to authorize a new service, or modify server, DNS or storage settings.

This only works well because I’m self-hosting 90% of the services I use, and they use a Keycloak as identity provider, and then don’t have to handle identity themselves.

This is why I’d prefer to see more identity federation – ideally the tokens the services see are short-lived, but the user doesn’t have to re-login every time either.

Re:Finding Pwned Passwords with 1Password by stordoff on Saturday February 24, 2018 @02:47PM (#16454931)
> Now compare it to the number of people who said that they can't take your site seriously until you have it.

I imagine some people use it as a signal - if you support 2FA, you are at least considering security well, even if they don't actually make use of it.

Re:Finding Pwned Passwords with 1Password by dsacco on Friday February 23, 2018 @11:47PM (#16451730)
> I'm talking about automated password rotation. A new 128-bit* random base64 password every month. Rotating credentials is important, even if you automate them.*

To be clear, you’re aware how absurdly long it would take to complete offline cracking for a single, randomly generated, 128-bit password, right? From a purely statistical perspective, what you’re advocating doesn’t actually make sense. It can only impose usability friction.

Unless you know a site’s password database has been compromised, you shouldn’t change the password. If it has been compromised, your password is so strong that you could honestly let just about every computer in the world try to crack it and still be reasonably confident in its continued security.

Password managers empower you to do that, but with a different password for every single service you use. You set it and forget it because you don’t have to do anything else. Simpler is better for users.

> For the same reason that Let's Encrypt only provides certificates with 90 days validity

I’m sorry, but no. This is utterly dissimilar to personal passwords. Public key certificates have limited validity because digital signatures cannot be revoked offline. The entire premise of a digital signature scheme and PKI is that you default distrust. Therefore, signers must renew instead of revoke, like a dead man’s switch. It doesn’t make sense to use this principle as a comparison for password security, because passwords are a secret used for access control, not authentication in the cryptographic sense of the term.

I think there is merit to the argument that public key authentication is better than passwords, but such a discussion should 1) include nuances, like the differences between authentication and access control, and 2) be mindful of cavets, especially with respect to usability. Under the current paradigm, passwords are not weak just because they do not share the same e.g. rotation characteristics as certificates, because they have very different use cases and threat models.

Re:Finding Pwned Passwords with 1Password by mnutt on Friday February 23, 2018 @11:22AM (#16447260)
How do password managers make password rotation any worse? If anything, they at least keep a record of which sites need password rotation.
Re:Finding Pwned Passwords with 1Password by kuschku on Friday February 23, 2018 @11:35AM (#16447366)
We used to have OpenID in the past, now that password managers exist, efforts to fix the problem at the root have been stalled.

In fact, Android implements now on OS level an API for password managers, but no way to easily authenticate through a third party app.

Password managers are "good enough" that few people care about better solutions anymore.

Personally, I'd prefer to see client side certificates, or OIDC login everywhere, with short lived session tokens, and proper U2F 2FA.

Re:Finding Pwned Passwords with 1Password by dsacco on Friday February 23, 2018 @11:37PM (#16451692)
> Ideally you'd rotate them every 60 days.

This isn’t correct. Password rotation is a function of desired cover time (how long you want to maintain confidentiality) and password strength (approximate entropy and complexity).

If you randomly generate a password with 20+ mixed case alphanumeric characters, it’s theoretically safe against offline brute forcing attempts for more time than the universe has existed. Statistically speaking, you gain virtually nothing by rotating such passwords unless you know they’ve been compromised. On the other hand, you impose a significant security liability through usability friction.

Re:Finding Pwned Passwords with 1Password by wlesieutre on Friday February 23, 2018 @10:31AM (#16446888)
This was me a couple months ago. Had one password that I reused on a bunch of websites where I didn't particularly care about security.

Eventually decided to give them all stronger unique passwords (because why not) and it was a pretty easy process because the password manager could show me all the sites with duplicate passwords.

Re:Finding Pwned Passwords with 1Password by dawnerd on Friday February 23, 2018 @09:02PM (#16451192)
And theres some sites where random passwords just don't work because of dumb password rules so hand making them is easier. Also still nice to know when a password, randomly generated or not, is released out there in the wild.
Re:Finding Pwned Passwords with 1Password by zie on Friday February 23, 2018 @10:16AM (#16446765)
well, let's say I run idiotService, and you login with a nice strong randomly generated passphrase, but since I'm idiotService, I just store it plaintext and check against it.. to make matters worse, some bad guy steals my password list, but I'm such an idiot I didn't even notice...

Troy hunt, in his ever-long quest of getting copies of these breaches, eventually gets a copy of all of my passwords and adds it to his database, and now suddenly, you the user get a warning, uhh.. this password is in the pwned-passwords DB... and now you know idiotService really is an idiot.

Re:Finding Pwned Passwords with 1Password by raverbashing on Friday February 23, 2018 @12:01PM (#16447554)
Because your generated "long and strong password" is not accepted in some sites, or cause problems or is just a PITA to type on mobile devices, or I can't copy and paste it for some reason or another, for example
Re:Finding Pwned Passwords with 1Password by ascagnel_ on Friday February 23, 2018 @04:31PM (#16449803)
Or because the password itself is leaked somehow (eg a DB of passwords that was stored incorrectly getting hacked, which happens with some degree of regularity). I use a "long and strong" password to lock a password manager, which itself generates long and strong unique passwords for each login (I use 1pw here, which is nice because it can also handle 2FA/rolling codes). I haven't yet found a better way of handling that at scale that isn't "write down your passwords on a piece of paper in clear-text".
Re:Finding Pwned Passwords with 1Password by Consultant32452 on Friday February 23, 2018 @11:56AM (#16447520)
I use a password manager and still have embarrassingly simple passwords for some things. The reason is that the most common place I'm "typing" this password is an obnoxious interface like a gaming console.
Re:Finding Pwned Passwords with 1Password by jzl on Friday February 23, 2018 @01:39PM (#16448297)
Lastpass has an awesome option when generating passwords for cases like this: "Make pronounceable". It will generate a password like "lickyusideno" (just generated that now) which is easy enough to remember between looking at the lastpass app on your phone and then typing it in through a console/netflix/etc interface.
Re:Finding Pwned Passwords with 1Password by taco_emoji on Friday February 23, 2018 @05:08PM (#16450048)
I wrote a little HTML/JS app to generate pronounceable passwords which alternate left-and-right hands. Mainly I use it for my AD logins at work, which I A) have to enter numerous times per day and B) have to change every 60 days. The "pronounceable" part makes them easy to remember for the first couple of days, and then the "easy to type" part means muscle-memory takes over so that it's barely and inconvenience.

Data source is a python script which trolls through /usr/dict/words and then counts the occurrence of each three-letter alternating-hand combination, outputting the counts. To start I pick a letter with 1/26 odds, then filter the triplets based on first letter, then continuously pick triplets based on the last two selected letters.

(I think this amounts to a Markov chain but I've not studied them well enough to know for certain...)

Re:Finding Pwned Passwords with 1Password by Bokagha on Friday February 23, 2018 @03:44PM (#16449431)
1Password actually has the same feature. You can separate the words with a hyphen, space, period, comma or underscore on generation to make it more human readable.
Re:Finding Pwned Passwords with 1Password by Consultant32452 on Friday February 23, 2018 @10:17PM (#16451440)
All of the bad password traits are rewarded in this scenario. You want a password as short as possible, with as many repeating characters as possible, etc.
Re:Finding Pwned Passwords with 1Password by blakesterz on Friday February 23, 2018 @10:18AM (#16446773)
"Clicking the Check Password button will call out to Troy’s service and let you know if your password exists in his database. "

I think the point is to see if any password you've come up with (either generated in 1password or on your own) has been breached and you don't know it. If you do have unique passwords for everything and you see that it's there, then you would know what's been pwned.

Re:Finding Pwned Passwords with 1Password by inetknght on Friday February 23, 2018 @10:23AM (#16446818)
1) Use password manager

2) get asked to help someone else at their machine

3) need to log-in to a remote resource under my own user to do something

4) password is in the password manager on my workstation on another floor

Solution? Should I:

* ask the person to give very exact and detailed instructions on what they need me to accomplish so that I can do that work from my own workstation?

* go up to my workstation and call the person who needs help and walk him through logging in as me?

* remote-login from their workstation to mine to copy/paste (and hope their workstation's clipboard is secure)?

* bring my password manager with me on my phone (and risk my passwords being pwned because phones are Not Secure)?

* write down 40 character password somewhere (stick-it note?) and hope I neither typo anything, nor allow others to read it, nor carelessly discard it?

* just use a password I made up and can easily remember?

I'm sure there's better solutions. Each one has their own annoyances.

Re:Finding Pwned Passwords with 1Password by heartbreak on Friday February 23, 2018 @10:34AM (#16446910)
> * bring my password manager with me on my phone (and risk my passwords being pwned because phones are Not Secure)?

As someone who uses this solution to your above-stated problem, I disagree with the assertion that phones are "Not Secure." Care to back that up?

Re:Finding Pwned Passwords with 1Password by yAnonymous on Friday February 23, 2018 @11:40AM (#16447409)
Where do I even start? I think it would be easier for you to tell me why you think phones are secure and then I tell you why you're wrong.
Re:Finding Pwned Passwords with 1Password by inetknght on Friday February 23, 2018 @11:27AM (#16447302)
Physical device small enough to be quickly stolen: Not Secure. (this is self-evident: physical access to device is Game Over)

Low battery requires plugging in a cable to charge; the cable may be a surreptitiously-installed data cable. I do not trust the hardware or software stack that handles the data cable to be secure.

SMS: Not Secure. http://www.cybersecuritytrend.com/topics/cyber-security/arti...

Wifi: Not Secure. https://www.bestvpn.com/privacy-news/wpa2-wifi-not-secure/

Many apps "require" silly amounts of permissions to the phone before they'll install. Apps' ability to read what's on screen, to be notified of clipboard changes, to listen to sounds; all when not even in the foreground. On my computer, I can easily check what apps and background services are running. Not so easily on a phone.

Re:Finding Pwned Passwords with 1Password by 0xfeba on Friday February 23, 2018 @01:53PM (#16448397)
> On my computer, I can easily check what apps and background services are running.

Did you audit the Intel AME, HD firmware, chipset, audio drivers, usb drivers, and everything else on your PC?

Re:Finding Pwned Passwords with 1Password by matthewmacleod on Friday February 23, 2018 @06:05PM (#16450414)
(this is self-evident: physical access to device is Game Over)

This is just totally not true.

I'd wager a fair sum that passwords stored on an iPhone, behind a decent layer of security, are entirely better protected from physical access than on any general-purpose computer.

Re:Finding Pwned Passwords with 1Password by inetknght on Friday February 23, 2018 @06:26PM (#16450524)
Passwords stored on a general purpose computer, behind a decent layer of security, are entirely better protected from physical access than on any phone I've ever used.
Re:Finding Pwned Passwords with 1Password by lox on Sunday February 25, 2018 @04:17AM (#16458021)
Yeah, the FBI totally breezed through the whole iPhone unlock thing. /sarcasm
Re:Finding Pwned Passwords with 1Password by wgjordan on Friday February 23, 2018 @11:07AM (#16447154)
Copy/paste the needed password from your workstation to a text file on a secure USB key, then use the key to copy/paste it into the login on the other workstation and delete the file.

> * remote-login from their workstation to mine to copy/paste (and hope their workstation's clipboard is secure)?

This option also risks leaving around credentials to remote-login to your workstation.

No sense worrying about the workstation's clipboard-security though- if the workstation itself is pwned or intentionally bugged, the password will be at risk from a keylogger or network-sniffing proxy when it's typed in anyway, so no avoiding that risk.

Option B is to ask yourself whether a 40-character impossible-to-write-down-without-typos password, phones are Not Secure level of security-paranoia is worth the tradeoff of inconvenience (it may be, depending on the nature of your work).

Re:Finding Pwned Passwords with 1Password by inetknght on Friday February 23, 2018 @11:25AM (#16447281)
All good points.

FWIW I currently write software which analyzes DNA; privacy and medical issues are real and definite concerns to me.

Re:Finding Pwned Passwords with 1Password by r3bl on Friday February 23, 2018 @10:41AM (#16446941)
If I anticipated such action could occur, I would use an "X random words" passphrase pattern.

It's long, it's random, you don't have to look at it, and is easily communicated to someone.

Heck, I do the same for answers to security questions in case I need to communicate an answer to it for whatever reason.

Re:Finding Pwned Passwords with 1Password by stordoff on Friday February 23, 2018 @01:53PM (#16448398)
Some passwords I need to memorise (e.g. the logon password for my primary machine), and others need to be input on devices where long, strong passwords would be unduly cumbersome (e.g. my Xbox/PSN accounts are never going to get the same strength I use elsewhere because typing long, mixed case + symbols passwords on a controller is a nightmare).
Re:Finding Pwned Passwords with 1Password by rootlocus on Friday February 23, 2018 @10:40AM (#16446935)
"long and strong" randomly generated passwords can be found in password dumps too.
Re:Finding Pwned Passwords with 1Password by craftyguy on Friday February 23, 2018 @10:43AM (#16446947)
> The way they implemented this is nice, but seems a bit pointless to me.

I've always thought that the best way to build a rainbow table is to create a 'password checking service' like this and have people fill it with their own passwords.

Re:Finding Pwned Passwords with 1Password by jedberg on Friday February 23, 2018 @12:51PM (#16447940)
If you read the details you'll see that's not the case here. They don't get your password or even the full hash.
Re:Finding Pwned Passwords with 1Password by technion on Saturday February 24, 2018 @02:35AM (#16452221)
The only way I can get a password that meets some of the more ridiculous "security" policies some places have is to go through the criteria and make one up myself.
Re:Finding Pwned Passwords with 1Password by twblalock on Friday February 23, 2018 @03:29PM (#16449265)
I'm more concerned about people using weak master passwords for their password managers. It's a single point of failure in the security of every other password they have.
Re:Finding Pwned Passwords with 1Password by chrisper on Friday February 23, 2018 @12:13PM (#16447650)
You can't generate every password. Some you need to remember, but it is good to store them in case you forget them.
Re:Finding Pwned Passwords with 1Password by dexterdog on Friday February 23, 2018 @10:30AM (#16446877)
I do it because lastpass/1pw/bitwarden/etc all seem to generate random passwords which are hard to use manually. If they do a "pronounceable" one it's all lower case or doesn't mix case other than randomly or capitalizing the first letter. Many of us like some kind of variation on xkcd's password generator. I haven't seen an implementation that does it the way I like so I wrote my own. I have that generate a password and then I put it into bitwarden (or whatever I'm currently using). I thank myself when I have to manually type the password into a device because I can look at it and remember it long enough to type it one time.

Also, some "long and strong" passwords are too long and/or string for sites that have poor password requirements.

Re:Finding Pwned Passwords with 1Password by notheguyouthink on Friday February 23, 2018 @10:48AM (#16447009)
I'm not sure what your requirements are, but 1password optionally generates passes from words. Eg:

> fracas homily unsaddle bonus pueblo victim

I vastly prefer it.. by leagues. With that said, I rarely use it. For my feeling of security I want to use many word combos, but it's very common for password input services to limit the number of characters I can use. Some of them (shockingly often) even truncate the password and accept it anyway, so now I don't even know what my password is.

Shame.

Re:Finding Pwned Passwords with 1Password by davidcollantes on Friday February 23, 2018 @10:11AM (#16446718)
It is pointless to me too. Yet, one of my co-worker told me: "Because even if not using crazy long random generated passwords, using a different one for each login is still a step in the right direction, and being able to remember 200 discreet passwords is hard for almost anyone."

Boggles my mind...