public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Roger J. H. Welsh" <rjhwelsh@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Coming up with a password that is very strong.
Date: Tue, 5 Feb 2019 17:42:09 +1300	[thread overview]
Message-ID: <20190205044151.dp6pqpnhoavst427@ponos> (raw)
In-Reply-To: <8d027455-f210-c399-f5a7-bfb05692cc5f@gmail.com>

Hi Dale,

On  Sun, Feb 03, 2019 at 11:47:35PM -0600 , Dale wrote:
> How do you, especially those who admin systems that are always being
> hacked at, generate strong passwords that meet the above?

I have a script for generating passwords the way I like (basically diceware on bash).

Something like:
FACTOR=$[ 2**(4*8)/$(cat "$WORDLIST"|wc -l) ]
cat "$WORDLIST" | head -n "$[ $(od -vAn -N4 -tu4 < /dev/random ) / $FACTOR ]" | tail -1

I use this in conjunction with
https://github.com/dwyl/english-words/blob/master/words.txt

As far as I understand, if you have about 96 bits of entropy you are
golden. 256 bits is unbruteforceable (at least within the realms of
physics apparently).
5 words = 94 bits (which is good enough for me)
14 words = 256 bits (which seems like a lot of typing)

I also have a messy spreadsheet for checking passwords.
https://github.com/rjhwelsh/gpg-tutorial/blob/master/password_checker.ods

I provide no warranty for my working. ;)

--

Roger Welsh
fpr: 2FCB 9E31 EA77 CDEC A3AE  5DD7 D54C C777 553A 180D


  parent reply	other threads:[~2019-02-05  6:20 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  5:47 [gentoo-user] Coming up with a password that is very strong Dale
2019-02-04 10:24 ` Peter Humphrey
2019-02-04 10:37   ` Neil Bothwick
2019-02-04 11:17     ` Mick
2019-02-04 11:48       ` [gentoo-user] " Nikos Chantziaras
2019-02-04 13:21       ` [gentoo-user] " Neil Bothwick
2019-02-04 13:43         ` Rich Freeman
2019-02-05  6:48         ` Dale
2019-02-05  9:55           ` Mick
2019-02-05 10:04             ` Michael Schwartzkopff
2019-02-05 10:18               ` Dale
2019-02-05 10:13             ` Dale
2019-02-05 11:21               ` Mick
2019-02-05 12:46                 ` Dale
2019-02-04 11:10 ` [gentoo-user] " Nikos Chantziaras
2019-02-04 19:38   ` Jack
2019-02-04 20:51     ` Neil Bothwick
2019-02-05 20:28     ` Mark David Dumlao
2019-02-05 21:17       ` Neil Bothwick
2019-02-06  2:41         ` Mark David Dumlao
2019-02-08 14:26         ` Kai Peter
2019-02-08 20:59           ` Neil Bothwick
2019-02-09  0:19             ` Dale
2019-02-09 10:06               ` Neil Bothwick
2019-02-09 10:42                 ` Dale
2019-02-09 16:02                   ` Alec Ten Harmsel
2019-02-13 16:31           ` Rich Freeman
2019-02-13 17:12             ` Mark David Dumlao
2019-02-13 19:17               ` Rich Freeman
2019-02-13 21:34                 ` Mark David Dumlao
2019-02-13 21:50                   ` Rich Freeman
2019-02-04 20:49   ` Dale
2019-02-04 20:59     ` Rich Freeman
2019-02-04 21:06       ` Neil Bothwick
2019-02-04 22:12         ` Dale
2019-02-04 23:18           ` Rich Freeman
2019-02-05  7:34             ` Dale
2019-02-05 14:13               ` Rich Freeman
2019-02-05 16:00                 ` Dale
2019-02-04 23:26           ` Mick
2019-02-05  7:55             ` Dale
2019-02-05 11:34               ` Mick
2019-02-05 13:05                 ` Dale
2019-02-05  8:41             ` Neil Bothwick
2019-02-05  9:28               ` Mick
2019-02-05 12:27     ` Nikos Chantziaras
2019-02-04 16:42 ` [gentoo-user] " Laurence Perkins
2019-02-04 18:39 ` Lee Clagett
2019-02-04 20:09 ` [gentoo-user] " Dale
2019-02-04 20:19   ` Rich Freeman
2019-02-04 21:39     ` Dale
2019-02-04 22:34 ` [gentoo-user] " Tanstaafl
2019-02-05  1:10   ` Dale
2019-02-05 19:49     ` Tanstaafl
2019-02-05 23:50       ` Dale
2019-02-06 18:13         ` Tanstaafl
2019-02-05  4:42 ` Roger J. H. Welsh [this message]
2019-02-10 16:12 ` Andrew Savchenko
2019-02-10 16:27   ` Dale
2019-02-10 16:59     ` Andrew Savchenko
2019-02-10 18:13       ` Mark David Dumlao
2019-02-10 22:44         ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190205044151.dp6pqpnhoavst427@ponos \
    --to=rjhwelsh@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox