From: Jude DaShiell <jdashiel@panix.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Password questions, looking for opinions. cryptsetup question too.
Date: Wed, 20 Sep 2023 13:54:57 -0400 [thread overview]
Message-ID: <8a2a5169-4c91-041-e6f5-15f9ddaee02d@panix.com> (raw)
In-Reply-To: <ZQsbYedTV5AVRSFR@sparta>
Another possibility is to write down encrypted passwords and don't
disclose encryption technique. The rot13 is worthless.
-- Jude <jdashiel at panix dot com> "There are four boxes to be used in
defense of liberty: soap, ballot, jury, and ammo. Please use in that
order." Ed Howdershelt 1940.
On Wed, 20 Sep 2023, Hoël Bézier wrote:
> Am Tue, Sep 19, 2023 at 12:36:13AM -0500 schrieb Dale:
> >In the real world tho, how do people reading this make passwords that no
> >one could ever guess? I use Bitwarden to handle website passwords and
> >it does a good job. I make up my own tho when encrypting drives. I'm
> >not sure I can really use Bitwarden for that given it is a command line
> >thing, well, in a script in my case. I doubt anyone would ever guess
> >any of my passwords but how do people reading this do theirs? Just how
> >far do you really go to make it secure? Obviously you shouldn't give up
> >much detail but just some general ideas. Maybe even a example or two of
> >a fake password, just something that you would come up with and how.
>
> For storing passwords, I use app-admin/pass.
>
> For choosing passphrases, I write sentences. I know having space character at
> a predictable frequence in the passphrase makes it easier to find out, but
> using phrases makes it easier to come up with very long passphrases (which, I
> believe, balances the space thing, though I’m no crypto expert), which are
> also easy to remember.
>
> Hoël
>
>
next prev parent reply other threads:[~2023-09-20 17:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 5:36 [gentoo-user] Password questions, looking for opinions. cryptsetup question too Dale
2023-09-19 8:26 ` Michael
2023-09-19 9:10 ` Jude DaShiell
2023-09-20 2:41 ` Dale
2023-09-20 2:59 ` [gentoo-user] " Grant Edwards
2023-09-20 4:49 ` Dale
2023-09-20 20:22 ` Frank Steinmetzger
2023-09-20 20:51 ` Rich Freeman
2023-09-20 21:56 ` Frank Steinmetzger
2023-09-20 6:47 ` [gentoo-user] " hitachi303
2023-09-23 10:57 ` Wols Lists
2023-09-19 10:00 ` Rich Freeman
2023-09-19 11:13 ` Dale
2023-09-19 11:47 ` Michael
2023-09-19 13:30 ` hitachi303
2023-09-20 2:52 ` Dale
2023-09-20 4:19 ` Dale
2023-09-20 12:28 ` Michael
2023-09-20 18:05 ` Frank Steinmetzger
2023-09-23 12:39 ` Wols Lists
2023-09-23 13:35 ` Dale
2023-09-23 14:00 ` Wol
2023-09-23 15:05 ` Dale
2023-09-23 16:08 ` Rich Freeman
2023-09-19 9:03 ` hitachi303
2023-09-19 9:13 ` Dale
2023-09-23 12:47 ` Wols Lists
2023-09-23 13:42 ` Dale
2023-09-23 15:44 ` Håkon Alstadheim
2023-09-19 9:16 ` Jude DaShiell
2023-09-19 11:22 ` Dale
2023-09-20 16:18 ` Hoël Bézier
2023-09-20 16:39 ` Jack
2023-09-20 17:54 ` Jude DaShiell [this message]
2023-09-27 9:43 ` [gentoo-user] " Nikos Chantziaras
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=8a2a5169-4c91-041-e6f5-15f9ddaee02d@panix.com \
--to=jdashiel@panix.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