From 82a4ce577b9da17e7eccc78b04b7e2e96b809b75 Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Fri, 24 Nov 2017 18:49:52 -0800 Subject: notes/updates --- notes/bugs.txt | 6 ++++++ notes/crypto.txt | 5 +++++ notes/drive.md | 7 +++++++ notes/typos.txt | 4 ++++ 4 files changed, 22 insertions(+) create mode 100644 notes/bugs.txt create mode 100644 notes/typos.txt (limited to 'notes') diff --git a/notes/bugs.txt b/notes/bugs.txt new file mode 100644 index 0000000..c4fa6fa --- /dev/null +++ b/notes/bugs.txt @@ -0,0 +1,6 @@ + +possible upstream bug: + => sync data in subdir + => stop client + => remove entire dir + => doesn't `del` on later sync diff --git a/notes/crypto.txt b/notes/crypto.txt index ea81a5f..0a80619 100644 --- a/notes/crypto.txt +++ b/notes/crypto.txt @@ -7,3 +7,8 @@ https://nacl.cr.yp.to/stream.html https://github.com/maidsafe/rust_sodium https://groups.google.com/forum/#!original/boring-crypto/BpUmNMXKMYQ/EEwAIeQdjacJ + +TLS is a pain, but if it (or some other standard) was used instead of the +current libsodium, it might be possible in the future to get kernel-mode +encryption going. + diff --git a/notes/drive.md b/notes/drive.md index 8148acf..9116117 100644 --- a/notes/drive.md +++ b/notes/drive.md @@ -18,3 +18,10 @@ The current path counts as an entry (eg, "/README" decomposes to "/" and Entry indexes are effectively 1-based (0 is the pubkey entry); don't correct for this. + +In children: +- Changes/edits to a path entirely replace the old entry index with the new + index. +- removals of an entry are done by writing a new entry with the same path, no + stat data, and with all child paths removed (of this index and the old + index). diff --git a/notes/typos.txt b/notes/typos.txt new file mode 100644 index 0000000..2198381 --- /dev/null +++ b/notes/typos.txt @@ -0,0 +1,4 @@ + +"check if all bites in the 2 bytes" + +"compresses nicely as its all contiguous ones on disk" -- cgit v1.2.3