public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Coming up with a password that is very strong.
Date: Sun, 10 Feb 2019 16:44:57 -0600	[thread overview]
Message-ID: <22f55689-62a8-f12b-53f2-7b542d2b1896@gmail.com> (raw)
In-Reply-To: <CAG2nJkM8unKj_+NY4Yhq9P+-eNTS4xVARLJN9VgfEPtervNKPw@mail.gmail.com>

Mark David Dumlao wrote:
> On Mon, Feb 11, 2019 at 1:00 AM Andrew Savchenko <bircoph@gentoo.org> wrote:
>> On Sun, 10 Feb 2019 10:27:32 -0600 Dale wrote:
>>> My password manager does that already.  The password I was trying to
>>> come up with was the master password which I must easily remember, be
>>> secure and be easy to type.  The other passwords I let the password
>>> manager generate and remember as well.  I don't type those so they can
>>> be anything.
>> The line above is approximately the same how I got one of my master
>> passwords. It is not that hard to remember 30-40 random chars.
>> Just try typing them several hundred times. I'm serious.
> That's one of the problems of secure password generation is that human
> memory is used backwards. Things become encoded permanently in our
> memory after the fact that we've repeated them several times, but most
> password generation utilities require you to have perfect memory
> first, THEN use repetition to enforce it.
>
> Both a managed password / algorithmic approach gets this more
> humanely. You need to first have a reliable way to generate the
> pssword, and if you typie it enough times, your brain will commit it
> to memory.
>
>


My biggest thing was to find a way to come up with it.  Most use some
famous quote or song and then each first letter or something with a few
numbers and symbols thrown in.  Thing is, I don't really have any of
those.  So, what I did, I based it on model numbers of some things I
like.  I threw in a few symbols as well just to make it harder. 

I might add, I used three password strength sites to sort of give me a
idea on strength.  I tried different methods to shorten the thing and
make it easier to type as well.  I actually ended up with a slightly
shorter password but one that the meters said would be harder to crack. 
I might add, the difference was large.  The original was something along
the lines of thousands of years.  The end result that was easier to type
and slightly shorter was millions of years.  I was able to put in more
symbols.  Those things help toughen up a password pretty quick.

What I find so interesting about this, everyone seems to have a slightly
or even very different way of doing this.  Even if a person is reading
this list and taking notes, I wish them luck trying to guess our
passwords.  Given the variety of methods used, I don't see how any tool
could be built that would guess any of our passwords in a short time
frame either.  Now if everyone else would put some effort into this
instead of using "passw0rd" or something as silly as that, the internet
would be a much safer place. 

I also ran up on some sites that discussed passwords that people
commonly used and some are just laughable but so bad one should cry. 
Some people are just plain idiots.  I might add, some sites restrict
passwords in ways that keeps a person from generating a really good
password too.  Some need to get with the current threat models instead
of living in the past when security wasn't such a issue. 

Interesting thread.

Dale

:-)  :-) 


      reply	other threads:[~2019-02-10 22:45 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
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 [this message]

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=22f55689-62a8-f12b-53f2-7b542d2b1896@gmail.com \
    --to=rdalek1967@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