From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Coming up with a password that is very strong.
Date: Tue, 5 Feb 2019 21:17:01 +0000 [thread overview]
Message-ID: <20190205211653.57d0b0dc@digimed.co.uk> (raw)
In-Reply-To: <CAG2nJkNMf5zV1ZS-w+e3r9DtQoiK0GLM9M3noHPbmuJ1C1xCLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Wed, 6 Feb 2019 04:28:49 +0800, Mark David Dumlao wrote:
> My own solution is actually very simple. I have a "secret algorithm"
> that incorporates several secrets with a predictable way to generate a
> site-specific secret. The end result is a 100% predictable way to
> generate unique passwords for every site that are cryptographically
> secure from each other (you cannot derive
> one from the other) which can be generated by any device using the
> appropriate tools.
The was a tool in portage this did this. I tried it but it did not work
in the real world because you couldn't set a rule for generated passwords
that matched the requirements of all sites, for example some require a
non-alphanumeric character while other sites only allow alphanumerics.
I can remember what the tools was called, although I'm pretty sure it
was written in Python. I'd be interested to know how you get around the
conflicting restrictions as this seems a good way to do things.
--
Neil Bothwick
MIPS: Meaningless Indication of Processor Speed
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-05 21:17 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 [this message]
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=20190205211653.57d0b0dc@digimed.co.uk \
--to=neil@digimed.co.uk \
--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