From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Coming up with a password that is very strong.
Date: Mon, 4 Feb 2019 15:39:13 -0600 [thread overview]
Message-ID: <75d871d1-b60f-6bc0-c2b0-d78220260fc8@gmail.com> (raw)
In-Reply-To: <CAGfcS_nTMxTGd-YqLXvTpRLn7xaZNC7UsWN7kp7AXPN0D26mPw@mail.gmail.com>
Rich Freeman wrote:
> On Mon, Feb 4, 2019 at 3:09 PM Dale <rdalek1967@gmail.com> wrote:
>> I'm not sure if one can convert that to NSA time or not. o_O The
>> password contains upper/lower case letters, couple symbols from up top
>> of the number keys and several numbers. None of which anyone would be
>> able to guess in any way. They have nothing to do with that list of
>> things not to use, birthdays etc. If a person was trying to just guess
>> it, even a best friend who knows me extremely well, they would not be
>> able to guess it much less the order of it. The only bad thing, it
>> isn't to easy to type. Of course, a really good password usually isn't
>> so . . .
> And do you use that password on only a single site?
>
> If you use it on more than one, then as soon as one of those sites is
> compromised it will sniff your password and then your password can be
> used on all the others without any cpu cycles wasted on brute-forcing
> it at all.
>
> That is the weakness of random passwords. Unless you use some kind of
> password manager you won't actually use a unique password on each site
> due to difficulty with memorization...
>
Right now, I'm coming up with a master password for LastPass and maybe a
new set of keys. I may use something different for my keys to your
point. My encryption thingy broke on Seamonkey, the keys are broken
somehow. I googled, tried some stuff but can't figure out how to fix
them so I revoked the things and am going to start fresh. Heck, only
one person ever uses them anyway. lol
Once I get logged into LastPass, I generate unique passwords with it for
each site. Depending on the site, I try to generate as long and use as
many characters as the site will allow. If it allows the symbols on top
of the number keys, I enable them. If it doesn't, I cut that off. If
it allows 20 characters, I set it to generate 20. It's not like I have
to remember it or even type it in either. I may as well be as secure
and random as possible. The master password is the current project tho.
Way back, I used to have three passwords. One fairly secure one for
financial type sites, one somewhat decent one for stuff like social
sites and one I could care less about. None of them would be easy to
guess but the complexity changed. Nowadays, I wouldn't even dream of
doing like that. Far to many script kiddys out there trying to steal
stuff. That doesn't even mention the pros and what they do.
You are right tho, reusing passwords is a really bad idea. It makes it
dead simple to hack everything else.
Dale
:-) :-)
next prev parent reply other threads:[~2019-02-04 21:39 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 [this message]
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
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=75d871d1-b60f-6bc0-c2b0-d78220260fc8@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