Repository navigation
Changed
- Visual Studio solution versioned with the repository (
Kubuno.Drive.slnx, generated by vskubuno, the naming of
every Kubuno repository): the server is the projectKubuno.Drive.Server, the frontendKubuno.Drive.Web, in
the solution folders Server, Libraries and Frontend, with the shared launch profile "Drive (Kubuno Core + browser)".
The crate and npm names do not change.
Fixed
-
Files kept on the server's local storage are found again on Windows and under symlinked storage
roots (shared storage layer updated to kubuno-storage 0.1.2). -
MariaDB and Oracle MySQL installs use the migrations written for them. The module now runs its
mysql-mariadbormysql-oraclemigration set when the database is MariaDB or Oracle MySQL, instead of the generic MySQL set. -
Drive starts on MySQL and MariaDB again. Migration 2 ("one live file per
name and folder") declared its uniqueness key as aSTOREDgenerated column
overfolder_id, whose foreign key isON DELETE SET NULL; both servers refuse
that (MySQL 8 with error 1215, MariaDB with error 1901), so the module stopped
at start-up. Each server now runs a variant of that migration
(migrations/mysql-oracle/,migrations/mysql-mariadb/) that declares the
columnVIRTUAL— same key, same unique index, same rule. The variants are
recorded under the original checksum, so nothing changes for a database that
already applied the migration. If an earlier start failed on it, delete the
failed row once (DELETE FROM drive._sqlx_migrations WHERE version = 2 AND success = 0) and restart. -
Database migrations keep the same checksum on every OS. The repository now
pins line endings to LF (.gitattributes), so a checkout on Windows no longer
turns SQL migrations, scripts, manifests or sources into CRLF. A database
migrated by a Linux build is therefore no longer refused by a Windows or macOS
build of the same version because its migration checksums differ. -
Merging two folders keeps the trashed files of the merged folder. Moving
or renaming a folder onto a same-named one (with "merge") used to drop the
source folder's trashed files; they now move into the destination and stay in
the trash, restorable, without overwriting anything there. -
Restoring a file whose name is now taken keeps both files. The restored
file comes back under a unique name (report (2).pdf) next to the file that
took its name. -
Storage quota is charged back exactly once when files are deleted for
good. Emptying the trash freed nothing from the quota, and the automatic
trash clean-up and permanent deletes left the space used by version history
counted forever. File and version sizes are now released together, once, and
the version history's stored copies are removed too. On SQLite installations
the quota counter was not updated at all; it now is. -
Renaming or moving a folder keeps every file pointing at its contents,
including files stored under a different name on disk; if the database step
fails, the folder is moved back on disk. -
No more duplicate copies of the same file. Two saves of a new document
arriving together (office drafts, Flow, App, PaintSharp files), or a save
racing the disk scan, could each create a file with the same name in the same
folder, often over one stored copy. A folder can now hold only one live file
per name: a concurrent overwrite updates that file, a concurrent upload gets a
numbered name, and the disk scan skips names already in use. Existing
duplicates are merged on upgrade: the most recently saved copy is kept, the
others' version history, shares, comments, tags, activity and star move to it,
and a duplicate with different contents becomes a version of the kept file —
nothing is deleted.drive:fscklists any that remain (--merge-duplicates). -
Module file registration with "overwrite" no longer deletes the contents it
registers. Re-registering a file at the location just written deleted the
previous record and, with it, those very bytes; the record is now updated in
place. -
Drive builds from a clean checkout again. The lockfile pinned two shared
crates (kubuno-modauth,kubuno-storage) to commits that no longer exist on
GitHub after their tags were moved, so a freshcargo buildcould not fetch
them. The lockfile now points at the commits the tags currently resolve to. -
Drive is fully translated again. English (and other non-French) users saw a
French "Mon Drive" page title and a French "Deux volets" entry, because the
title used a translation key that existed in no language and the two-pane view
had no translations at all. Both are now translated in every supported
language.
Added
- Downloads answer byte-range requests (
206 Partial Content,Accept-Ranges: bytes), so a video
or an audio file can be sought without downloading it again, and a PDF viewer can fetch only the pages
it shows. - Drive now runs on PostgreSQL, MySQL/MariaDB or SQLite. The database engine
is an administrator's choice, set in configuration ([database] engine) and
read at start-up; the same build connects to whichever is named. SQLite needs
no server at all, which turns a single-machine or evaluation install into a
one-line affair. Existing PostgreSQL instances keep working unchanged. - Open Drive in Visual Studio. The repository now ships a ready-made solution
(Kubuno.Drive.slnx) with the server and frontend projects and a launch profile
that starts both, so contributors can build and debug Drive from Visual Studio
without generating the solution first. Per-machine files (obj/,.vs/, user
settings, the local SDK feed) stay out of version control. drive:fsckmaintenance command.kubuno-drive drive:fscklists the
files and versions whose contents are missing from storage and the files that
share one stored copy, account by account (--owner,--json). It changes
nothing unless asked:--split-sharedgives each file its own copy, and
--trash-missingmoves files whose contents are gone to the trash, where
their owner can see them. It exits with code 2 when it finds a problem.
Changed
- File search reworked to behave identically on every database. A file's
name and extracted text are reduced to their word stems (with accents folded)
when the file is indexed, and a query is matched the same way, so a search
returns the same results and the same ranking whichever engine backs the
instance. Approximate "typo" matching on names is no longer offered.
Security
-
The storage rescan is no longer reachable without authentication. The
maintenance route that re-synchronises files on disk with the database (adding
and removing entries) could be triggered by anyone, including through the
public API. It now requires the module's internal secret and is refused to
clients. Internal calls are compared in constant time and refused when the
module has no internal secret configured. -
Thumbnails, previews, the video and audio players, downloads (files, archive members, fonts) and the
image editor no longer rely on the access-token cookie the web client used to keep readable by page
scripts. They load with short-lived signed tickets bound to your session and to the exact file.
Saving from the image editor now uses your session instead of a token read from local storage.
Requires a Kubuno core that issues signed tickets (POST /api/v1/auth/tickets) and@kubuno/sdkwith the signed-URL helpers. -
Deleting a folder for good no longer leaves broken files behind or destroys
other files' contents. A permanent folder delete (Shift+Delete, deleting from
the trash, the WebDAVDELETE, the module and admin APIs) moved the folder's
files to the root of the drive while wiping the folder's directory on disk, so
those files showed up at the root with their contents gone, and any other file
whose bytes happened to live in that directory lost them too. The whole folder
is now deleted consistently — subfolders, files (trashed ones included),
version history and thumbnails — and the bytes are only removed after the
database change is committed and only when no remaining file still uses them. -
Emptying the trash, or deleting a trashed file for good, no longer erases a
live file with the same name. A file uploaded under the name of a trashed
file in the same folder shares its storage location; purging the trashed copy
deleted the live file's contents. Shared contents are now kept. -
A new file no longer takes over the contents of a trashed file with the same
name. Uploading, creating, renaming, moving, copying or restoring a file
under the name of a trashed file in the same folder wrote over the trashed
file's contents, so restoring it brought back the wrong data. Every file now
gets a storage location that no other file or version uses; the name shown in
Drive is unchanged. -
File and folder names can no longer escape their folder. A rename to a
name such as../../other.txt, or a folder name containing\(a path
separator on Windows), could place bytes outside the folder, or even outside
the account's own storage. Such names are now refused. -
Security fixes from the shared database layer (kubuno-db 0.9.0). The
database password can no longer appear in a log through the debug output of
the database settings. A search now keeps at most 16 distinct words (set for the
whole instance by the core's[search] max_terms), so a single request can
no longer overload the database. -
PDF and XML readers updated to patched releases. The PDF text extractor
could be made to overflow the stack by deeply nested objects
(RUSTSEC-2026-0187), and the XML reader could be driven into quadratic time or
unbounded memory by a crafted document (RUSTSEC-2026-0194, RUSTSEC-2026-0195).
Both parse files that users upload. -
Database driver updated past an unfixable advisory. The previous line
pulled in an RSA implementation vulnerable to a timing side-channel
(RUSTSEC-2023-0071) for which no fix will ever exist. The new line does not
depend on it at all. An unsoundness in the event-listener it relies on
(RUSTSEC-2026-0221) is closed at the same time. -
Input validation library updated. The version in use carried
RUSTSEC-2024-0421 through its domain-name parser, which accepted Punycode
labels that decode to plain ASCII — a mismatch an attacker can use to make two
different names look like one.