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: Tue, 5 Feb 2019 04:18:02 -0600	[thread overview]
Message-ID: <824a5aee-acdf-719c-e673-6ac2c2e02c15@gmail.com> (raw)
In-Reply-To: <0c453cde-6777-a7df-6c20-d21e985a057a@sys4.de>

Michael Schwartzkopff wrote:
> Am 05.02.19 um 10:55 schrieb Mick:
>> On Tuesday, 5 February 2019 06:48:53 GMT Dale wrote:
>>
>>> Sort of picking a random message to reply to here.  Someone sent a reply
>>> off list about checking passwords on my system with tools available.
>>> They also mentioned not trusting strength meters which I can get since
>>> they pass some obvious passwords.  I used three meters and some sort of
>>> common sense as well.  I found cracklib-check after some digging.  I
>>> used that to try to check my password and get this weird response. 
>>>
>>> -su: me-supper-secret-password-here;): event not found
>>>
>>> I'm going to try to emulate my password without actually posting it, for
>>> obvious reasons.  You all are smart enough to understand why.  ROFL  It
>>> has some of the following 'stuff' in it.  !sdER*ark4567#  As you can
>>> tell, I use some of those things on the tops of the number keys.  It
>>> seems that confuses cracklib just a bit.  BTW, I was running that as
>>> root just to be sure it wasn't a permissions issue.  I tried a few
>>> different things but it seems the "!" is triggering that at least, maybe
>>> others too.  The command works fine with just normal stuff.
>> Hmm ... I don't get such problem here, when I run cracklib as a plain user:
>>
>> $ cracklib-check
>> password
>> password: it is based on a dictionary word
>> p4ssw0rd
>> p4ssw0rd: it is based on a dictionary word
>> p477w0rd
>> p477w0rd: OK
>> !sdER*ark4567#
>> !sdER*ark4567#: OK
>> helloworld
>> helloworld: OK
>> reallysecurepassword
>> reallysecurepassword: OK
>>
>> LOL!
>>
>> Could it be something to do with your terminal/shell?  I've run the above with 
>> bash in a urxvt terminal.
>>
>>
>>> That leads
>>> me to this question.  Is there a tool I can use/install that will test a
>>> password, try to crack it if you will, that will work regardless of the
>>> characters used?  In other words, it doesn't mind the things on top of
>>> the number keys. 
>>>
>>> BTW, I've also whittled it down to something a little easier to type
>>> too.  Feel sorry for any poor fool trying to just guess it.  lol  May
>>> have better luck with P vs NP.  ;-)
>>>
>>> Thanks.
>>>
>>> Dale
>>>
>>> :-)  :-) 
>> I've used app-crypt/johntheripper in the distant past, but you'll need a good 
>> word list for it to be useful.  Some of the wordlists I had found at the time 
>> were too big to download over dial-up!  :p
>>
> A good password also has to be memorizable. See:
>
> https://xkcd.com/936/
>
>
> Mit freundlichen Grüßen,
>


That's the problem.  I want one really good password that would be
virtually impossible even for someone who knows me to guess.  Doing that
and being able to remember it plus be relatively easy to remember
complicates things a lot.  While at it, I'd like it to be hard to crack
as well.  Even with these password test tools, that is proving to be
hard to know for sure.  I have one that I know would be hard to guess
and I think it would be hard to crack as well but I don't know that last
part for sure, yet anyway. 

Thanks.  It's a work in progress still. 

Dale

:-)  :-) 


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

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=824a5aee-acdf-719c-e673-6ac2c2e02c15@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