WebDAV server — your NanumOS as a file store
What it is
A file store that runs inside NanumOS. Phones, Macs, Windows PCs and Linux machines in the same home or office put files in it and take them out. It works like a mailbox: only someone with the key (an account and password) can put in and take out, and nobody sees anyone else's mailbox. The zcloud vault can be kept in it too.
What to do now: type the one line under "Make an account" and the one line under "Start the server" in a terminal.
How to use it
Make an account
Start the server
service dav start- Check: Zeus's check (
/doctor) gets a "WebDAV server" row — accounts, requests, how full the fullest store is; it turns to "fault" when the server stops.
Connect from other devices
- Mac: Finder › Go › Connect to Server ›
http://NanumOS-address:8797/— the account name and password. - Windows: File Explorer › Map network drive › the same address. Windows normally refuses to send a password over plain
http://(https will fix that; until then set the registry valueBasicAuthLevelto 2). - Linux and the Mac command line:
rclone(webdav),cadaverandcurl -T file http://…/all work. - zcloud:
zcloud join http://NanumOS-address:8797/zeus.kdbx device-name— make one account per device and give them all-T zcloudso they share one store.
How it works
In the mailbox picture: the server keeps a ledger (which mailbox holds a letter of which name) and a pile of letters (the contents) apart. A letter's name is written in the ledger only and never reaches the file system, so a trick like "../" cannot open another place. If an upload is cut half way, the new letter is thrown away in its temporary place and the old letter is untouched.
Technical details
- Standard WebDAV class 1 and 2 (RFC 4918): OPTIONS, GET/HEAD (Range), PUT (streaming, chunked, 100-continue), DELETE, MKCOL, COPY/MOVE (Overwrite, Destination), PROPFIND (depth 0 and 1), PROPPATCH (dead properties kept), LOCK/UNLOCK (exclusive and shared, always with a time limit), If, If-Match and ETag done exactly. The conformance suite litmus 0.13 passes 104 of 104.
- Names are UTF-8; the decomposed (NFD) Hangul a Mac sends is stored composed (NFC). A name may be 255 bytes (85 Hangul syllables).
- Account passwords are stored as Argon2id (19 MiB, 2 passes); a good password is remembered as a keyed BLAKE2b tag so only the first request is slow. Five wrong tries lock that address out for 30 seconds.
What this server takes
- What it stores: the files you upload with their names, sizes, change times and attached properties, and the account names with the Argon2id hash of each password (the password itself is not kept).
- What it does not take: it does not read or index file contents and sends nothing anywhere; its log holds the request line (method, address) and the account name, never a password or file contents.
- Where to: nowhere. It stays in this machine's memory and this machine's storage.
Frequently asked
Why is my password refused? It may be under 8 characters, or five wrong tries from the same address locked it out for 30 seconds. An upload fails (507). The account's limit (-Q) or the machine's free memory is used up. **My Mac makes ._name files. Finder stores extra information in separate files; they are kept as ordinary files. What happens to locks when the server restarts?** Locks live only in memory and are released. Files, properties and accounts stay.
NanumOS 0.1.8349 · 2026-11-16