From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Encrypted drive setup at login and locking on logout.
Date: Mon, 6 Jul 2020 11:17:24 +0100 [thread overview]
Message-ID: <20200706111724.4a19f02c@digimed.co.uk> (raw)
In-Reply-To: <d4fd30c4-ce62-f84d-6995-86517b0acd5d@iinet.net.au>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On Mon, 6 Jul 2020 17:05:48 +0800, William Kenworthy wrote:
> > By the way, the USB stick will have instructions about things after
> > I'm buried or whatever. I plan to keep the USB stick in a safe and
> > share the password with the person that will be taking care of
> > things. When I'm gone, they can open the USB stick to access files on
> > what to do and such. Until I'm gone, they won't know what is on the
> > stick or have access to it. Getting older makes one think about these
> > things. :/ External drives will have things that when I'm gone, they
> > gone too.
> >
> Paper in a sealed envelope in a safe (bank safety deposit box etc) ...
> too many things to go wrong with an encrypted USB.
I too have a USB stick in the safe, but it's not encrypted. As you say,
too much to go wrong that way. I actually use 2 sticks, just in case one
of them corrupts.
--
Neil Bothwick
Barnum was wrong....it's more like every 30 seconds!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-06 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 2:23 [gentoo-user] Encrypted drive setup at login and locking on logout Dale
2020-07-04 3:49 ` Francesco Turco
2020-07-04 13:01 ` Michael
2020-07-06 4:49 ` Dale
2020-07-06 5:24 ` William Kenworthy
2020-07-06 6:37 ` Dale
2020-07-06 9:05 ` William Kenworthy
2020-07-06 9:46 ` Dale
2020-07-06 10:17 ` Neil Bothwick [this message]
2020-07-06 11:02 ` Rich Freeman
2020-07-06 8:21 ` Neil Bothwick
2020-07-06 9:53 ` Dale
2020-07-06 10:19 ` Neil Bothwick
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=20200706111724.4a19f02c@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