From 161e120dfa312659569bb35c7c789a03f89c0840 Mon Sep 17 00:00:00 2001 From: Erin Abicht Date: Mon, 17 Apr 2023 23:02:19 -0400 Subject: [PATCH] Basic filesystem encryption info --- src/development/design/filesystem.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/development/design/filesystem.md b/src/development/design/filesystem.md index ce700f4..2a4c385 100644 --- a/src/development/design/filesystem.md +++ b/src/development/design/filesystem.md @@ -44,6 +44,7 @@ const CHUNK_SIZE: u16; // Example static chunk size struct Chunk { checksum: u64, extends: bool, + encrypted: bool, uuid: Uuid, data: [u8; CHUNK_SIZE], } @@ -52,6 +53,7 @@ This struct is then encoded into bytes and written to the disk. Drivers for the It *should* be possible to do autodetection, and maybe for *Actors* to specify which disk/partition they want to be saved to. Compression of the data should also be possible, due to `bincode` supporting [flate2](https://lib.rs/crates/flate2) compression. +Similarely **AES** encryption can be used, and this allows for only specific chunks to be encrypted.[^encryption] ### Reading On boot, we start executing code from the beginning of the disk (the boot partition, although that's meaningless at this point). @@ -75,6 +77,8 @@ Again, whether actors can: will be determined via [capabilities](/development/design/actor.md#ocap) +[^encryption]: Specific details to be figured out later + [^find_chunk]: Currently via magic. I have no idea how to do this other than a simple search. Maybe generate an index, or use a **UUID**? [^free_chunk]: Again, no idea how.