From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-191703-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 99D1A1382C5
for <garchives@archives.gentoo.org>; Sun, 7 Jun 2020 01:50:23 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 82211E0972;
Sun, 7 Jun 2020 01:50:17 +0000 (UTC)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 3A0AAE08A2
for <gentoo-user@lists.gentoo.org>; Sun, 7 Jun 2020 01:50:17 +0000 (UTC)
Received: by mail-qt1-x829.google.com with SMTP id k22so11964660qtm.6
for <gentoo-user@lists.gentoo.org>; Sat, 06 Jun 2020 18:50:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=subject:to:references:from:openpgp:autocrypt:message-id:date
:user-agent:mime-version:in-reply-to;
bh=P667VpLnQsqvUm5dwITZzN1Q07ZlRF1aTTjkvr1trl8=;
b=gZvAlCjtWLTknVwv3B9LawTKslbJanHaMJdKFD8vvZX2oSVh3yfd2+4fNl08T400Ly
0UFAVkMd01EW0Iy9ng7daJ71cJMBgUS+/G5jlBkFUeyMRM5AiQUwbJ5gSMpWeKbPnPpV
hbPrwmqnSRZ0njScDyztgYd5dATt7POvRX8DWHnNOaJIhhICRsNU8KpaFuICyMV/c8GU
ZhOYgaTHwIxqJgTyCgpMLFQA/KcbQzeEo/+X8hqhFqkbL9EneJospr2FqwqTTLJ3D7/o
RC2R0TXUHqTXYoCk+NimeJ8+4UZGjcUERaQf5dCQD263+AHOWVVVwGt3HxXE7xSPDssk
lSTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt
:message-id:date:user-agent:mime-version:in-reply-to;
bh=P667VpLnQsqvUm5dwITZzN1Q07ZlRF1aTTjkvr1trl8=;
b=mXoLqzazX3c5sRydp5cMKgsQF3EyMLsboaXQTZZ0JFTyjM2aGskm1UP7o1aonwynJJ
2aImmJfTjiEG4lroy1y/Zu9emXgct5/f/NfzLLkx0Lyq2yrgzL/ETfhGcveq12kO3fPJ
Lxq7DChrLJq90DaznbAR2MskxOapIxxyCSeEvlWJ8hN59yzp5Ebj9R0XlPWAHCne3ecE
T9Z5FrbNr0EUxqWtRNdY9hNMJJ5nH52TuNuq7D1a2GPtSaB7WsZJmd90Bes71ddQwc3j
L01wwWlpmRJZ6axOzsrnlPWAUignhriu/HZvhA3hz1w0YGAT5XzolGk8yTm0oPQq6fbE
fJ6g==
X-Gm-Message-State: AOAM532aUHNEG6WQaaZzZrfK8DVAtc/8n2Bxib+Fkrhmz6EzLcAuEV/C
UimsoISCMx77cwYu+bSojYY=
X-Google-Smtp-Source: ABdhPJxYMlLUoppiqKCiUsO6MQclSiNkT2V7QNLtl8Lkndk70j1EtY8Qu1f4lyEPLFms1eK/Uqgprg==
X-Received: by 2002:ac8:7a77:: with SMTP id w23mr17597526qtt.111.1591494615386;
Sat, 06 Jun 2020 18:50:15 -0700 (PDT)
Received: from [192.168.0.100] (adsl-074-188-244-109.sip.asm.bellsouth.net. [74.188.244.109])
by smtp.gmail.com with ESMTPSA id o66sm3767368qka.60.2020.06.06.18.50.14
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Sat, 06 Jun 2020 18:50:14 -0700 (PDT)
Subject: Re: [gentoo-user] Encrypting a hard drive's data. Best method.
To: gentoo-user@lists.gentoo.org
References: <ddcf7e41-ef39-eae8-ba36-82efc057a1ee@gmail.com>
<7e55092b-1914-da09-cb33-25aea63d2b22@gmail.com>
<CAGfcS_=Qt6=hjTWpPvN+zHabagnQvazeqgZu9Qi74utWPeuj0A@mail.gmail.com>
<6a9ae564-14be-aa10-e0d3-d50fd82e3e3b@gmail.com>
<CAGfcS_kxEU_y7d8cTbg7sbXOtdKgaUmt7i_05vYVFahc1SBtTQ@mail.gmail.com>
<7e2ee8c9-7956-39a4-e31b-6a3f40d08da9@gmail.com>
<CAGfcS_ncL5UcqwHBDAUEJXV5ePP36in+MVCjbBcgBHj3gRfQgQ@mail.gmail.com>
From: Dale <rdalek1967@gmail.com>
Openpgp: preference=signencrypt
Autocrypt: addr=rdalek1967@gmail.com; prefer-encrypt=mutual; keydata=
mQINBFxc7MgBEAC+zrgEdqJJiDe/UDAB+ScmferXWfJTVjbVT2T4DQ7jiLrgP9aNUo1HioNF
mrU3JPOCR32gvZyTbY1+niO5+VSo/+pSqQ785h6ZDj1klMkrg6tEzGnf2MNBpBj4houZwxQ+
WDKKTg2M9F+lv8wTIdR/JQn+hSviktLMtrghQlyLhpapsLXWLA6gMFebpQYwxUwemvan8ddX
lQvJe9FGyFYvBi0dp1gl10F2O+DVZJxvX8xkX+yImVlhVJiC31gXHRcj+Qlo7gprlU7TIieF
Uow6/ZvYKJ26pztVdFCg5w0rMJkF/x8Zd4A6wnuptiAPmWaQ1+YKgYDonbDUgwqFSx5/lN5z
DGZ4LlioxeUTTPVvZsqBIeDz6jNFA583OYbo1/S26dqrvTFf2DKlsvoDpVfAhNlwJPjoixs0
X3FNqPv+M10n4kq5Iz7Q9E3O4s/nfFIYGocEslVka7zZPkXSaHbsn+KJlY8XV6qxtCEdh0/V
XX1+1aU2J74M0JikWhpwxTZ1dP5aOyWSPPEgFFIRW6xwwC02SoRH9a7mggfGYp/YjPlONNaT
SCL8sgRfvmq3D0XTbLyTjSbExxkfKDmbePQagawDE3TlI/oivHf1JaAcbwMb3LZuU4TGcOIl
5D+x7q0MUIeCop0ZFOwAnqW3AVVNvsBkv2KN+IHJryWAf0/iMQARAQABtBtEYWxlIDxyZGFs
ZWsxOTY3QGdtYWlsLmNvbT6JAk4EEwEIADgWIQTZ7suruPBaS60bCYXvEM/XWu+ZnAUCXFzs
yAIbIwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRDvEM/XWu+ZnN+7D/4/1dNG4aCz0+v+
0dcjV5tY1feYEWCdHKyDzxWBxlCpd/0NPRQeNY4VMjbCl/sq7GkXi/c2SbfWDQ5BQRkkExG1
pSwuXSIehGok/4fpTi3HDAguRvzdCqlKPt7me05FyiC/WnpY5GOlJ3ruGw2qABv/RmV2q5b/
tkq7h1y1f16DTNr3/nsj8HzHcrHdXdL4kaYChSOe/dbQR9Stqak7eMyR+iwvrJMNF/CGl70P
2x5ybsXMDzRVOqNcpa5ZdhEMTVh6+vC1SOmm1BFMF8XCqBEvBbcHWDQmGYTdNCsS/ADm8CBl
gvjJgLdIsAzoMu4WHQDFnzXAoArqFWgAf53isOS4AWrv29tF9b8Aa1vb7h5JEa+ArcMsA6Gl
X38+GY6WXXaxKI9n3PTCWu9tPGnRh7mABjnwEosDDqmzw8aTAYECb3avDuGY2rmcjgh4H6RE
w08d63j1T4d5J9wlm4TGtW/VHgbUFkATEdH3Acl/EjFiyqTiX7p8kU6Reu5enIkogA93xoQh
Rmy7ZiST/5LN+ZkaOdyjIw0L+5KalslN9SKt809YxgJ6kPo657LNTFPiFvFA46/SEWcBYrzq
Xk0wEW0gBRWf+BqN0qRhU0/EQ+QfRdLLFg2xtUePwlheYLXxfyDLrdCCOLWYpkzbjCZHLS4u
69smbvR9S9KBDNzJybxEWrkCDQRcXOzIARAA5IGRWTqaM44IJgBYghZg2fGj0Am7KWPhE7V7
T/EEe7vVSUEFqHtlHzI4ZK6Q0AZ9uAEjE8IJIQ7KoTjzNqAtabP0vp3s0szgtJlsZ+8vGKlQ
my7fvzSrdoQL0Xn7CEwJYFXJ1EMUcYIQeoHG1cUAaXx73k9BFbjwjnUeMrqlV/ZovQlg7duW
nESfQ7HZu5NrtYyY3jPMUouxiO9WQPh+IHxZbt1absF2VcvRAymD32RxGvMPbw6ChMRD/p9O
4PH7M5rXaxr78NXQX9E48vrI00f1cYb9NSN1HnSV8cW3jKObVjdBk6jPQwrMvdpgdQhUB9aZ
HS/9mC9mmAgiXKyCpzXe7FPB6QznSfn4GIaC/luy1e6SLUkJhRK/niB+gq+Mfxg2zXNuDUTI
cMGmpDCp3kgUoorkaltk8RW09io95BkXrGhcDNuSGZfAParBc7RXyYpbIcax8St7tEAd2oFh
4seYOPUlzuhGrPpqR/91wrFc4E1260GKauSr4UhMJv6tygBwyC0mmBMKi+ZXw6ZdZxA5fg7y
35P3TILjznCXXTDgRHq9A3NknKRMcgFacX6eIhANkMFo6oJVjuEgy1dvu1wFfDq7c+i8GAHu
L4pYzyXYu6PporlNNU0xSwdVgzM/uuK0lt+UxCimgC+YR3IezgDcbfudb7h9dGIwL+bbPL0A
EQEAAYkCNgQYAQgAIBYhBNnuy6u48FpLrRsJhe8Qz9da75mcBQJcXOzIAhsMAAoJEO8Qz9da
75mcXZ4P/1YXgWDZek7mhzrf6uaQzMxa92P89HeWz4PlgB/32symeEFAV04WazzBZffI8AYY
rGA1Xmu/2VaB9+FOODyKhUWBc2UL0NRWBk6POwboyTdKlclmpixaN9zLcBt0YLejoRfN1B/5
aQf9/lUDZMnAiCyz0FgeqEMUshldmwWC35RqnjrCbbuk2vIqSH6BLDIXU6jQrLHE1DF0ai41
wLtQFAFXPhn45n0ZwYhVs4Z32z4sjXrIvgBgCaXa4HM+L1Klne0KiNM8ReFTTpTE0SgyDOSZ
O3MOa2n77i6JbVtsbiFYnNeP3J9S/l3jevGpZEtNQOKrIm1MW8jGuHWtsDeMkT/mCcSodlkt
PxIo+mMK9GpGvG2hW80LiohqNfUbNwAmr3blOYY4URPXPRnEnPs4pmTmL5owjw2dkg145i9I
D42Tq+XZ6YtWt3SGzGbAYow6XwTwZ5NFAzV9UQuCGrDw4KWan6O6Z+VIYWsn0UMZlu1Obxna
aocofkaUCbISK26kImuD1aA8juSHC18Qv1xUage6/UakbSxyDtACqt6hOVFKX3IA59ApdNRT
+2x3iCmlvF9MJsGgFq6IpqL+Fk7iWV8Kjbz0wQOId6N9+JdQh3LrLaS7a1PowUm1z9DK5/O0
Yg+gpDnEOOFI7WM5u7a7FSM2Z/LXGVwel/0eWvLk9tN6
Message-ID: <b788f50e-601c-7ff0-057f-c93e2c2f51a4@gmail.com>
Date: Sat, 6 Jun 2020 20:50:13 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Firefox/60.0 SeaMonkey/2.53.2
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
In-Reply-To: <CAGfcS_ncL5UcqwHBDAUEJXV5ePP36in+MVCjbBcgBHj3gRfQgQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------3BA2627B8B3ABDACBA50D5C3"
X-Archives-Salt: 7fcb13cf-1379-4eb3-9040-9b9aee33be92
X-Archives-Hash: 78a205548f0a79561dc1ad2c141ca245
This is a multi-part message in MIME format.
--------------3BA2627B8B3ABDACBA50D5C3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Rich Freeman wrote:
> 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.
>
My take. Bad password, easy to guess, easy to crack because it is
simple or common; not very secure even if the password is changed since
one could use the old password in certain situations and get at the
data. Good strong password, changed or not; hard to crack even if the
whole drive is taken.
Moral of the story. Have a good strong password and keep your mouth
shut about what the password is, unless you want that person to spill
the beans. Or you plan to knock them off later. ROFLMBO
I'm not storing the secrets to some new weapon that will destroy the
world and everything on it, including the roaches. Well, that last one
might be OK. lol I just want it so that when I fall into the cremation
chamber or a cemetery plot, it won't be easy for a person to access the
drive. I'm good at the keeping password to myself bit. Still thinking
on killing all the roaches tho . I'd keep that secure but I wouldn't
mind being rid of those. :/
I think I need to watch a youtube video on this tho. I want to watch a
person not only install it but actually use it. For example, what
triggers it asking for a password and what does it look like? Is it
pretty fast, take a few seconds or what? I got a lot of questions but
they are things that can't be answered easily in text. Yea, gotta go
visit youtube. Test drive youtube-dl again.
Dale
:-) :-)
--------------3BA2627B8B3ABDACBA50D5C3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Rich Freeman wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGfcS_ncL5UcqwHBDAUEJXV5ePP36in+MVCjbBcgBHj3gRfQgQ@mail.gmail.com">
<pre wrap="">On Sat, Jun 6, 2020 at 8:47 PM Victor Ivanov <a class="moz-txt-link-rfc2396E" href="mailto:vic.m.ivanov@gmail.com"><vic.m.ivanov@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
On 06/06/2020 21:12, Rich Freeman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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."
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<br>
<br>
My take. Bad password, easy to guess, easy to crack because it is
simple or common; not very secure even if the password is changed
since one could use the old password in certain situations and get
at the data. Good strong password, changed or not; hard to crack
even if the whole drive is taken. <br>
<br>
Moral of the story. Have a good strong password and keep your mouth
shut about what the password is, unless you want that person to
spill the beans. Or you plan to knock them off later. ROFLMBO<br>
<br>
I'm not storing the secrets to some new weapon that will destroy the
world and everything on it, including the roaches. Well, that last
one might be OK. lol I just want it so that when I fall into the
cremation chamber or a cemetery plot, it won't be easy for a person
to access the drive. I'm good at the keeping password to myself
bit. Still thinking on killing all the roaches tho . I'd keep that
secure but I wouldn't mind being rid of those. :/ <br>
<br>
I think I need to watch a youtube video on this tho. I want to
watch a person not only install it but actually use it. For
example, what triggers it asking for a password and what does it
look like? Is it pretty fast, take a few seconds or what? I got a
lot of questions but they are things that can't be answered easily
in text. Yea, gotta go visit youtube. Test drive youtube-dl
again. <br>
<br>
Dale<br>
<br>
:-) :-) <br>
</body>
</html>
--------------3BA2627B8B3ABDACBA50D5C3--