diff options
| author | @syxhe <https://t.me/syxhe> | 2025-01-02 23:59:40 -0600 |
|---|---|---|
| committer | @syxhe <https://t.me/syxhe> | 2025-01-03 00:01:14 -0600 |
| commit | 36dc7e18b66bb374d4c67a7f526c088636eaf9a2 (patch) | |
| tree | fc6554c9e2b40d30958321459cab4fde4d0116ca /notes.txt | |
| parent | 03c5fce0220d3e5d02d320f925a3b9401a397729 (diff) | |
Filter out . and .. folders from scan results
Diffstat (limited to 'notes.txt')
| -rw-r--r-- | notes.txt | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -5,9 +5,9 @@ also encrypt the /root dir as well. Running as a daemon and setting things up in | |||
| 5 | a good idea as well | 5 | a good idea as well |
| 6 | 6 | ||
| 7 | vxgg was not atomic in its encryption, in that if the encryption was in progress and interrupted for whatever reason, the original | 7 | vxgg was not atomic in its encryption, in that if the encryption was in progress and interrupted for whatever reason, the original |
| 8 | file would be "irrecoverably" (as in vxgg had no error checking and couldn't tell the difference between an encrypted and | 8 | file would be "irrecoverably" fucked (as in vxgg had no error checking and couldn't tell the difference between an encrypted and |
| 9 | unencrypted file other than through filename. You could manually unfuck the file yourself if you had the key, but it would be a | 9 | unencrypted file other than through filename. You could manually unfuck the file yourself if you had the key, but it would be a |
| 10 | long and tedious process) fucked. I can't possibly make the entire operation of reading and writing to a file atomic, but I can | 10 | long and tedious process). I can't possibly make the entire operation of reading and writing to a file atomic, but I can |
| 11 | make the action of "encrpytion" atomic; or, at least, I can make the encryption seem atomic through a cheat: hard linking. Turns out | 11 | make the action of "encrpytion" atomic; or, at least, I can make the encryption seem atomic through a cheat: hard linking. Turns out |
| 12 | 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 | 12 | 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 |
| 13 | 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 | 13 | 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 |
