On Sun, Jun 23, 2024 at 11:56:18AM +0000, Anon Loli wrote: > On Sat, Jun 22, 2024 at 03:28:37PM -0300, Crystal Kolipe wrote: > > On Sat, Jun 22, 2024 at 06:03:06PM -0000, Stuart Henderson wrote: > > > If this is really important, I suggest going to buy another drive to > > > plug in and dd to rather than trying to do anything complicated. > > > > Definitely. If the only copy of the key is in RAM, then time is of the > > essence. > > I know.. I have a spare drive that I can enable if only I were to not have a > problem with the computer detecting the drives (they aren't in /dev at all, > but > dmesg is reading them OK), as it is said in the other mailing thread > "Installer..." > > I'll get back to you guys after we fix that issue (if we do, otherwise I'll > have to do a different approach to enabling the hard drive which would be bad > becaues I want that drive to work as it is, in that computer) >
Okay, I've enabled the drive now, how do I approach this? I want the drive that's receiving the data copy to be encrypted, and it'll have to be over ssh, so I'm assuming some combination of DD and SCP? I've looked on the internet now, and it seems like dump/restore are perfect for this (and even faster than dd?) So maybe something like `dump af /dev/sd3i | ssh receiving-computer "restore xf -"` But where would the sd3i end up then and how? would it turn in a file, or become a /dev/sd3i copy on the receiving computer? If you don't respond, I'll search the internet and try to do it on my own (for the 1st time) and possibly overwrite something again lol Would be great if I could find some great read about this
