Live data from Hacker News

Show HN: Correct Horse Battery Staple password generator

correcthorse.pw

91–99 of 99 posts

Re: Show HN: Correct Horse Battery Staple password generator

#91
I have bookmarked this site for my own personal use. I also shared it with my co-workers in the IT dept.

I think your site works well on selling itself if you assume the audience is coming from HN. From what I have observed, your site does not market itself well to a typical corporate IT dept who are not all programmers.

I think if we want to promote wider adoption of this good password technique, we'll need a different approach.

This is not a criticism-- You've done a job I admire. I think I might fork it and make another version that is approachable to a wider audience. Thank you!

Re: Show HN: Correct Horse Battery Staple password generator

#92
post #88

Earlier quoted context omitted.

I'd imagine the risk is pretty great, for the same reason I wouldn't paste a password here that I use. Sure, you may not know who I am, but if you were the site itself you get a ton of information on me.. which is more than I'd like you to know if you _also_ know one of my passwords. I agree, the risk is minimal. Nevertheless.. security, heh.

The site doesn't know the password, though-- it's generated clientside.

Will you be inspecting the code every single time it loads to ensure that has not changed? You are receiving this code from an untrusted 3rd party every time you visit. There is a big difference to trusting a known entity like lastpass, 1password, etc, all of whom are vulnerable to supply chain attacks. It is another thing entirely to trust a random website on hackernews.

Payload decoders and password generators are some of the biggest honeypots out there. Combining this with an attack taking advantage of hidden form autofill, you could gain quite a bit of information to go along with that password.

Re: Show HN: Correct Horse Battery Staple password generator

#93
post #88

Earlier quoted context omitted.

The site doesn't know the password, though-- it's generated clientside.

Will you be inspecting the code every single time it loads to ensure that has not changed? You are receiving this code from an untrusted 3rd party every time you visit. There is a big difference to trusting a known entity like lastpass, 1password, etc, all of whom are vulnerable to supply chain attacks. It is another thing entirely to trust a random website on hackernews. Payload decoders and password generators are…

If I were to use it, I'd probably just pull my own copy off github.

If I were to recommend novices to use it-- I'd tell them to use a password manager locally, and something like that to generate a secure password to get into their own machine locally / get into their password manager-- which mitigates most of the risk if it turns rogue.

Re: Show HN: Correct Horse Battery Staple password generator

#94
post #87
post #56

Problem with generators and this scheme, they allow regeneration. Most people not using the first version, they generate a new until they like it enough to stop, which is not that random anymore as they think.

A mild amount of regeneration doesn't hurt, though. If you generate 4 and pick your favorite, you've shaved less than 2 bits of entropy off.

It's just a bare minimum that you reduced, if you add some preference it's worse than that. I did some test, maybe I'm just lucky, but i got password with a word starting with b at the 3rd generation, and i got adjective-noun pair in that order at the 5th generation.

Re: Show HN: Correct Horse Battery Staple password generator

#95
post #94
post #87

Earlier quoted context omitted.

A mild amount of regeneration doesn't hurt, though. If you generate 4 and pick your favorite, you've shaved less than 2 bits of entropy off.

It's just a bare minimum that you reduced, if you add some preference it's worse than that. I did some test, maybe I'm just lucky, but i got password with a word starting with b at the 3rd generation, and i got adjective-noun pair in that order at the 5th generation.

> It's just a bare minimum that you reduced

No, it's the -maximum- that I reduced entropy by. If I choose randomly from 4 possible passwords, I've shaved off --no entropy--.

If I choose with a strongly predictable preference (say, everyone knows I'll pick the password that's first alphabetically) I've shaved nearly 2 bits off the probable search space: you probably only need to look in the first 1/4th of the search space.

Choosing with some subtle, individual preferences is something inbetween.

Re: Show HN: Correct Horse Battery Staple password generator

#96
post #93

Earlier quoted context omitted.

Will you be inspecting the code every single time it loads to ensure that has not changed? You are receiving this code from an untrusted 3rd party every time you visit. There is a big difference to trusting a known entity like lastpass, 1password, etc, all of whom are vulnerable to supply chain attacks. It is another thing entirely to trust a random website on hackernews. Payload decoders and password generators are…

If I were to use it, I'd probably just pull my own copy off github. If I were to recommend novices to use it-- I'd tell them to use a password manager locally, and something like that to generate a secure password to get into their own machine locally / get into their password manager-- which mitigates most of the risk if it turns rogue.

well then you wouldn't be using this or any other website, and this entire conversation would be moot :).

Re: Show HN: Correct Horse Battery Staple password generator

#97
post #95
post #94

Earlier quoted context omitted.

It's just a bare minimum that you reduced, if you add some preference it's worse than that. I did some test, maybe I'm just lucky, but i got password with a word starting with b at the 3rd generation, and i got adjective-noun pair in that order at the 5th generation.

> It's just a bare minimum that you reduced No, it's the -maximum- that I reduced entropy by. If I choose randomly from 4 possible passwords, I've shaved off --no entropy--. If I choose with a strongly predictable preference (say, everyone knows I'll pick the password that's first alphabetically) I've shaved nearly 2 bits off the probable search space: you probably only need to look in the first 1/4th of the search s…

> with a strongly predictable preference

No, your example has nothing to do with preference, your method (picking out of 4) just less random than picking from one (the first).

Preference is, when certain passwords more likely to be picked than others or at those passwords less likely to be stepped over to generating a new one. Wtih strong preference you regenerate until you got that preferred password, for example you prefer short words and the attacker know that, at first trying combinations with short words has better chance to cracking the password.

Re: Show HN: Correct Horse Battery Staple password generator

#98
post #97
post #95

Earlier quoted context omitted.

> It's just a bare minimum that you reduced No, it's the -maximum- that I reduced entropy by. If I choose randomly from 4 possible passwords, I've shaved off --no entropy--. If I choose with a strongly predictable preference (say, everyone knows I'll pick the password that's first alphabetically) I've shaved nearly 2 bits off the probable search space: you probably only need to look in the first 1/4th of the search s…

> with a strongly predictable preference No, your example has nothing to do with preference, your method (picking out of 4) just less random than picking from one (the first). Preference is, when certain passwords more likely to be picked than others or at those passwords less likely to be stepped over to generating a new one. Wtih strong preference you regenerate until you got that preferred password, for example yo…

You're just talking past me, bro. Regenerating and picking your favorite from a few is reasonable and isn't a big entropy penalty (the penalty is easily bounded).

Infinitely re-rolling until you get the exact phrase "correct horse battery staple" obviously has a severe entropy penalty, and this is not a reasonable course of action.

Re: Show HN: Correct Horse Battery Staple password generator

#99
post #98
post #97

Earlier quoted context omitted.

> with a strongly predictable preference No, your example has nothing to do with preference, your method (picking out of 4) just less random than picking from one (the first). Preference is, when certain passwords more likely to be picked than others or at those passwords less likely to be stepped over to generating a new one. Wtih strong preference you regenerate until you got that preferred password, for example yo…

You're just talking past me, bro. Regenerating and picking your favorite from a few is reasonable and isn't a big entropy penalty (the penalty is easily bounded). Infinitely re-rolling until you get the exact phrase "correct horse battery staple" obviously has a severe entropy penalty, and this is not a reasonable course of action.

> You're just talking past me, bro.

Sorry for over explaning, but I feel it necessary.

Sticking with your example and making more formal. Name it pick function and let its three modes, random, deterministic and preference. In the random mode, the probability of picking one from the inputs are equal to picking to any other. In the deterministic mode, with the same inputs the function always picking the same and the probability of others are zero, but if the inputs change or any input, it could change the picked one. In the preference mode the function not just picking one, but making a sorted list of the inputs. In the preference mode, changing one input not changing the others sorting. In this mode using pick function on several inputs you got some information about the inputs overall probability distribution aka entropy (more precisely entropy is the measure of that).

The important from this, determinism not imply preference, but not random also. Cryptographic hash functions doing the extreme version of this determinism, the output is well "distributed", but not random. (PS: Sometime that characteristic called pseudorandomness, that is how PRNGs works with random seed)

Deterministic pick applied to random pick just less random than random pick alone on the same set, because random pick has the maximum of the entropy and adding some deterministic part just reducing that. But most people not picking with a well distributed deterministic function in their mind, more likely they pick with preference, which is I think much worse. So, that why I call it the bare minimum.

Post reply on HN