public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Coming up with a password that is very strong.
Date: Tue, 5 Feb 2019 14:49:19 -0500	[thread overview]
Message-ID: <71aa9151-e07d-0838-29c9-fca0240e7af8@libertytrek.org> (raw)
In-Reply-To: <1d42622d-ab7c-5673-3f8e-4bc52ddfcfc2@gmail.com>

On 2/4/2019, 8:10:57 PM, Dale <rdalek1967@gmail.com> wrote:
> Tanstaafl wrote:
>> I've been using a little Firefox Addon called Passwordmaker for many,
>> many years, and despite all of its warts, I've been loathe to give it
>> up, even though it will never be upgraded to work as a WebExtension.
>>
>> 2 things I loved about it -
>>
>>  a) it doesn't save the password locally, only info about the
>>     site/account, and
>>  b) you can use an unlimited number of Master Passwords
>>
>> I'm looking at migrating to KeePassXC, and even though I really hate the
>> idea of saving the actual password - Passwordmaker simply generates the
>> password on the fly each time based on certain specified criteria (ie,
>> the site URL, username, password length, etc for each account - one
>> technique I adopted shortly after assisting in updating the
>> Passwordmaker website eases my mind about it...
>>
>> This is a simple technique I strongly recommend that everyone employ,
>> especially if you use a Password manager (like LastPass or KeePass)...
>>
>> It is uncrackable (well, as long as it isn't the CIA or NSA that wants
>> to crack it and they are willing to kidnap/torture you to do so).
>>
>> You sit down and come up with a ... call it a 'password modification
>> protocol' ... whereby, you always modify your generated/stored password
>> in a specific way before pressing enter.
>>
>> For example, you delete characters 3, 5 and 7, then add 2 characters to
>> the beginning and 2 to the end.
>>
>> It is very simple, and negates worrying about someone stealing your
>> password vault.

> I tried to find it just to see how it works but it isn't listed.

What... Passwordmaker (the old one I still use and why I keep an old
Firefox 56 portable version around)?

> From what you wrote, you may want to at least check into LastPass.

I did a massive amount of research (including LastPass), and settled on
KeePassXC for a good reason.

> Still, I'm sure there is a tool that will suite your needs.

? Its like you didn't really read my email. I already said, I'm
migrating to KeePassXC. But my complaint is, nothing works like
Passwordmaker (again, it doesn't store passwords, can only use one
Master Password).

> I'm not sure I understand what you mean password modification protocol. 
> It sounds like you change your master password each time you use it.

No, I'm talking about the saved (or in Passwordmakers case, generated)
password, not the Master Password.

Doing this with the Master Password wouldn't make any sense.


  reply	other threads:[~2019-02-05 19:49 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 [this message]
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=71aa9151-e07d-0838-29c9-fca0240e7af8@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --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