From 36dc7e18b66bb374d4c67a7f526c088636eaf9a2 Mon Sep 17 00:00:00 2001 From: "@syxhe" Date: Thu, 2 Jan 2025 23:59:40 -0600 Subject: Filter out . and .. folders from scan results --- notes.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'notes.txt') diff --git a/notes.txt b/notes.txt index fb6f283..66af513 100644 --- a/notes.txt +++ b/notes.txt @@ -5,9 +5,9 @@ also encrypt the /root dir as well. Running as a daemon and setting things up in a good idea as well vxgg was not atomic in its encryption, in that if the encryption was in progress and interrupted for whatever reason, the original -file would be "irrecoverably" (as in vxgg had no error checking and couldn't tell the difference between an encrypted and +file would be "irrecoverably" fucked (as in vxgg had no error checking and couldn't tell the difference between an encrypted and unencrypted file other than through filename. You could manually unfuck the file yourself if you had the key, but it would be a -long and tedious process) fucked. I can't possibly make the entire operation of reading and writing to a file atomic, but I can +long and tedious process). I can't possibly make the entire operation of reading and writing to a file atomic, but I can make the action of "encrpytion" atomic; or, at least, I can make the encryption seem atomic through a cheat: hard linking. Turns out that you can make a file in /tmp, fill it with a whole bunch of shit, then hardlink it to somewhere else on the drive, and the file's contents will persist after a reboot. The idea here is to open a file in /tmp, write the encrypted contents to it, and then -- cgit v1.2.3