Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Depending on your threat model this will be very insufficient.
Discs have provisions for bad sectors, they have backup sectors, so if a sector gets too many errors, or has been written to too many times, disks can set aside that sector never to be written to again. So you can have unencrypted data just sitting there ready for somebody to read it
All of the operations indicated in the above post, rely on the file system behaving, and not at the disc level. So superblocks inodes journals and other file system specific data structures could be completely missed. Some file systems store user data inside of these special structures for efficiency purposes such as locality of reference, and time locality.