public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Encrypting a hard drive's data. Best method.
Date: Sat, 6 Jun 2020 21:04:39 -0400	[thread overview]
Message-ID: <CAGfcS_ncL5UcqwHBDAUEJXV5ePP36in+MVCjbBcgBHj3gRfQgQ@mail.gmail.com> (raw)
In-Reply-To: <7e2ee8c9-7956-39a4-e31b-6a3f40d08da9@gmail.com>

On Sat, Jun 6, 2020 at 8:47 PM Victor Ivanov <vic.m.ivanov@gmail.com> wrote:
>
> On 06/06/2020 21:12, Rich Freeman wrote:
> > Maybe we're miscommunicating, but it seems like you're moving the
> > goalposts here.
> > ...
> > Your original point was, "The problem here is that a leaked header
> > immediately means a compromised volume."
>
> I believe we're on the same page and it's indeed due to miscommunication
> and I suspect this is where the main point of miscommunication lies.
> You're taking my statement out of context. No doubt, I most certainly
> could have phrased this part better and made it clearer. It may not have
> been obvious but that sentence was aimed specifically in the context
> where a weak password is used or, especially, when a password has been
> compromised and how being able to change said password might have little
> effect. In which case the point still stands - when a password is
> compromised, there is a possibility that changing said password may not
> necessarily be the end of the matter as the (old) header may or may not
> have been leaked too either as part of the same or a previous attack -
> not necessarily involving physical access.

I think we're on the same page and just talking past each other.  I
didn't catch that as being the intended context, and in the scenario
you describe you are of course completely correct.

Thanks for bringing this point up though, as it isn't really something
I'd given much thought to.

-- 
Rich


  reply	other threads:[~2020-06-07  1:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06  4:37 [gentoo-user] Encrypting a hard drive's data. Best method Dale
2020-06-06  7:14 ` J. Roeleveld
2020-06-06  7:16 ` J. Roeleveld
2020-06-06  7:49   ` Dale
2020-06-06 10:32     ` Michael
2020-06-06 14:14       ` antlists
2020-06-06 11:05     ` Rich Freeman
2020-06-06 13:31       ` Victor Ivanov
2020-06-06 13:57     ` antlists
2020-06-06 14:10       ` Rich Freeman
2020-06-06 15:05         ` Jack
2020-06-06 14:18       ` antlists
2020-06-06 15:07       ` Dale
2020-06-06 19:02         ` J. Roeleveld
2020-06-06 14:07 ` Victor Ivanov
2020-06-06 18:51   ` Rich Freeman
2020-06-06 19:38     ` Victor Ivanov
2020-06-06 20:12       ` Rich Freeman
2020-06-07  0:47         ` Victor Ivanov
2020-06-07  1:04           ` Rich Freeman [this message]
2020-06-07  1:50             ` Dale
2020-06-07  8:08               ` Dale
2020-06-07  9:07                 ` antlists
2020-06-07 18:23                   ` antlists
2020-06-09 20:24                     ` Dale
2020-06-09 21:30                       ` [gentoo-user] Encrypting a hard drive's data. Best method. PICS attached Dale
2020-06-07 10:33                 ` [gentoo-user] Encrypting a hard drive's data. Best method Rich Freeman
2020-06-07 11:52                 ` Victor Ivanov
2020-06-07 12:43                   ` Victor Ivanov
2020-06-07  7:37         ` antlists
2020-06-06 15:07 ` Frank Steinmetzger
2020-06-06 20:21 ` Sebastiaan L. Zoutendijk
2020-06-07  1:54   ` Dale
2020-06-10  6:59 ` Dale
2020-06-10  9:52   ` Michael
2020-06-10 21:02     ` Dale
2020-06-10 13:37   ` Victor Ivanov
2020-06-10 20:52     ` Dale
2020-06-11 21:51       ` Victor Ivanov
2020-06-11 22:17         ` Dale
2020-06-11 23:08           ` Victor Ivanov
2020-06-12  2:00             ` 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=CAGfcS_ncL5UcqwHBDAUEJXV5ePP36in+MVCjbBcgBHj3gRfQgQ@mail.gmail.com \
    --to=rich0@gentoo.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