". . . . . ." is a good password

[bukzor]

It seems like the "repeat" strategy should apply to multiple-character runs.

[analytically]

+1

[mgifford]

This makes sense to me. Are other pattern checks useful like /././././././.

[TheChown]

It might also be worthy of note that
.--. .- ... ... .-- --- .-. -..
represents the word "password" in morse code. (and perhaps mistakenly reports a crack time (seconds): 1.2393165958871756e+35).
I felt that this was worth mentioning for the sole fact that if symbol pattern substitution (from a alphanumeric domain into a multi symbol range) can be identified, not only can OP's ". . . . . ." be detected as a insecure, but any basic stenography can also be detected.

[JulioPotier]

  ²  ²

(space space square space space square)
is also a 6 chars, "strong" password.
2 repeated patterns containing 2 repeated chars.

[tracker1]

@BoiteAWeb makes me think that maybe a trim should be done before checking.. (I tend to trim any password inputs in case of extra characters with copy/paste.

[JulioPotier]

nono, never trim a password, i can decide to start my password with a space, this is not forbidden.

[tracker1]

@BoiteAWeb given how many times copy/paste includes extra leading/trailing whitespace and the resulting error, and confusion... it's probably better to not allow it... maybe not in this tool, but in practice... imho.

[stramel]

I agree with @BoiteAWeb.

[lowe]

as of 3.5.0, '. . . . . .' is no longer a good password! the new implementation of repeat_match catches multi-character repeat sequences.