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 10:27:32 -0600	[thread overview]
Message-ID: <f758e593-7ae9-945c-583b-54148ec4e59a@gmail.com> (raw)
In-Reply-To: <20190210191213.f143979ac631765a9dbb6837@gentoo.org>

Andrew Savchenko wrote:
> On Sun, 3 Feb 2019 23:47:35 -0600 Dale wrote:
>> Howdy,
>>
>> Some may recall me mentioning using LastPass to manage my passwords. 
>> Obviously, it can generate very strong passwords that are different for
>> each site.  It can also remember them as well which makes things more
>> secure than using just a few passwords for all sites.  One for things
>> like financial sites, maybe a less secure one for some site you still
>> want reasonably secure and a even weaker one for sites you don't care
>> about hacking, and hackers likely won't either.  I know some people who
>> do this even today.  Heck, ages ago, I was one of them.  Things change
>> tho.  Some passwords can be hacked in seconds by a desktop computer,
>> including my own if I had the software and knowledge to do it. 
>>
>> The one thing about most all password managers, they have a master
>> password.  That one password unlocks the rest.  Trick is, having that
>> one be a good one that is easy to remember, type on a keyboard and be
>> secure, virtually unhackable but also unforgettable.  I've had what used
>> to be a strong password for a while.  Thing is, with today's computing
>> power, it really isn't anymore.  While no one could just guess it, it
>> could be cracked/hacked I'm sure.  I need to come up with a new one that
>> meets the requirements I just mentioned.  Strong, easy to remember, easy
>> to type but won't forget.  I've read that using maiden names, years of
>> birth or whole dates of birth, actual names, pet's name, words in a
>> dictionary and a whole list of other things makes it easier, especially
>> if you post a lot on social media, for hackers to use against you.  I'm
>> trying to avoid that sort of thing obviously and have a couple ideas but
>> am curious as to what method others use, without exposing to much detail
>> since this is public. 
>>
>> How do you, especially those who admin systems that are always being
>> hacked at, generate strong passwords that meet the above?  I've googled
>> and found some ideas but if I use the same method, well, how many others
>> are using that same method, if you know what I mean.  ;-)  Just looking
>> for ideas. 
> 1) Install app-admin/apg.
> 2) apg -a1 -m40
>
> Best regards,
> Andrew Savchenko


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. 

Goes to show tho, there is yet another tool to come up with passwords. 
lol 

Dale

:-)  :-) 



  reply	other threads:[~2019-02-10 16:27 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 [this message]
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=f758e593-7ae9-945c-583b-54148ec4e59a@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