From 01e8a406c1dac25b6f5d051e7a8a7fadfe7c1ba7 Mon Sep 17 00:00:00 2001 From: Siyuan Ren Date: Sat, 20 Apr 2024 23:21:59 +0800 Subject: [PATCH] Update readme about --format --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bc1746e..242e83c 100644 --- a/README.md +++ b/README.md @@ -103,9 +103,9 @@ The **lite** format simply encrypts filenames and file contents separately, simi The **full** format maps files, directory and symlinks in the virtual filesystem all to regular files in the underlying filesystem. The directory structure is flattened and recorded as B-trees in files. -The lite format has become the default on Unix-like operating systems as it is much faster and features easier conflict resolution, especially when used with DropBox, Google Drive, etc. The full format, however, leaks fewer information about the filesystem hierarchy, runs relatively independent of the features of the underlying filesystem, and is in general more secure. +The lite format is the default as it is much faster and features easier conflict resolution, especially when used with DropBox, Google Drive, etc. The full format, however, leaks fewer information about the filesystem hierarchy, runs relatively independent of the features of the underlying filesystem, and is in general more secure. -To request full format, which is no longer the default, run `securefs create --format 2`. +To request full format, which is no longer the default, run `securefs create --format full`. ## Design and algorithms