Rich Freeman wrote: > On Sat, Jun 6, 2020 at 8:47 PM Victor Ivanov <vic.m.iva...@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 :-) :-)
