this post was submitted on 22 Jun 2024
37 points (93.0% liked)
Linux
48149 readers
740 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Threat model is me protecting myself from myself.
Incoming XY problem.
I want to prevent myself from reinstalling my system. The trick I came up with involved the use of files that couldn't be disk cloned. However, if it's far far easier to accomplish it through other means, then please feel free to enlighten me on this.
Ok, I'm still not clear on exactly what you're trying to achieve as I can't quite see the connection between somehow preventing certain files being duplicated when cloning the disk and preventing yourself from reinstalling the system.
Bear in mind that reinstalling the system would replace all of the OS, so there's no way to leave counter-measures there, and the disk itself can't do anything to your data, even if it could detect a clone operation.
If what you're trying to protect against is someone who knows everything you do accessing your data, you could look to use TPM to store the encryption key for your FDE. That way you don't know the password, it's stored encrypted with a secret key that is, in turn, stored and protected by your CPU. That way a disk clone couldn't be used on any hardware except your specific machine.
Premises:
Therefore, I would lose those very important files if I were to attempt a wipe. If said files are important enough for me to reconsider wiping, then the act of protecting them from copy/mv/clone has fulfilled its job of preventing me from reinstalling the OS.
I understand.
Very interesting. A couple of questions:
This seems like a very complicated way to achieve your goal! It sounds like sitting yourself down and giving you a stern talking to might be a beter aporoach.
Having said that, if you have these very important files that you don't want to lose, please make sure they're backed up somewhere off of your machine. Storage fails, and it's a horrible feeling losing something important. Unfortunately doing so would defeat the approach you're thinking of.
This might be a case of needing to reframe the question to get to the cause of the issue, and then solve that. So, why do you want to make it hard to reinstall your machine? Is it the amount of time you spend on it, the chance of screwing it up, needing it working, has it become a compulsion or something else? Maybe if we can get to the root of the issue we can find a solution.
With regard to TPM, it's basically just a key store, so you can use it fir anything really, althought it's normally used by generating a TPM key and using it to encrypt the key that's actually used to encrypt your data, storing the encrypted key with the OS. Just reinstalling won't wipe the TPM, but unless you made an effort to save the encrypted key it'll be gone. Given your problem statement above it just adds to the data you'd need to save, which isn't helpful.
You're probably right. But, it ensures a surefire method if accomplished.
Thank you for your concerns!
Makes sense.
I want to set it up in a particular way to ensure maximum productivity. But I'm afraid that I'll not go through with it (as has happened a lot in the past). Thus, making it impossible to reinstall should enable me to go through. As I wouldn't have any other choice.
The amount of time spent unproductively. Yes.
Nope. I haven't had a serious breakage since over one and a half years. I think I'm managing splendidly.
Don't really have particular problems related to keeping my system up and running.
Not sure what you meant with this.
I believe I touched upon this earlier in this comment. I just want to be very productive.
Uhmm..., I feel as if I should properly read up on this. Have you got any pointers you would recommend?
Sorry for the slow reply, life occurred.
I think I understand where you're coming from with the desired to be productive and not reinstall. I think I've been there too! One thing that I can suggest, if you do have the time, is to learn a system like Ansible and use it to setup and configure your machine. The discipline of keeping all of the config as source rather than making ad-hoc changes reduces the chance of thinking you'll make just one little change and breaking something, and, if something does go wrong, you can get back to your working configuration quickly.
Bearing in mind that there really isn't anything you can do to stop yourself if you're really determined to not lose the data, because if you can read it at any time you can back it up, the closest you are likely to come is something like creating new key with GPG then using the TPM to wrap your secret key and deleting the original. That way the key is only usable on that specific machine. Then use the key-pair to encrypt your 'guard' files. You can still decrypt them because you have the wrapped secret keys and you're on the same machine, but if you wipe the drive and lose those keys the data is gone. The TPM wrapping prevents you from taking the keys to a different machine to decrypt your data.
There's an article with some examples here,
Having said all of that, this still doesn't help if you just clone the disk as all of the data, including the wrapped key and the encrypted files will be cloned. The one difference there is that the serial number of the hard drive will be different. Maybe you could use that, combined with a passphrase as the passphrase for your GPG key, but we're getting into pretty esoteric territory here. So you could generate a secret key with a command like:
Where
/dev/sdbis the device your root partition is on.zenityis a handy utility for displaying dialogs, there are others available. In this use it just prompts for a passsword. We then concatenate the drive serial number fromlsblkwith the password you entered and hash the result. The hashing is really only a convenient way to mix the two without worrying about the newlinelsblkspits out. Don't record the result of this command, but use it to set the passphrase on your newGPGkey. Wrapping the secret key in the manner the article above suggests is a nice extra step to make it harder to move the drive to another machine or mess around in that sort of way, but not strictly necessary as that wasn't in the scope of your original question.Now you can encrypt your file with:
gpg -e -r <your key name> <your file>'. That will produce an encrypted version ofcalled.gpg. To decrypt the file you can getgpg` to use the hashing command from above to get the passphrase with something like:Once you've tested that you can decrypt the file successfully you can remove the original, plaintext, file. Your data is now encrypted with a key that is secured with a passphrase made of a string you know and the serial number of your disk and optionally wrapped with a key from the TPM that is tied to your physical machine. If you change the disk or the machine the data is irretrievable (ignoring the caveats discussed above). I think that's about as close to your original goal as you can get. It's rough around the edges, and I'm not sure I'd trust my data to it, but I believe it'll work. If you do something like this, please test it thoroughly, I can't guarantee it!