docs: keep the server's data folder private while it is recovered; Start with Windows row agrees with setup
The Windows README told an administrator to run icacls /reset /T on a data folder created by an unelevated console run, which let every local user read the database, the TLS key and the temporary admin password until the next successful start. It now takes ownership with takeown /A /R and removes only the console account's entries with icacls /remove:g, so nobody else gains access at any step. The 2026-10-12 Start with Windows decision said the uninstaller leaves the StartupApproved value; setup removes it with the entry, as the later Task Manager state row says. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
This commit is contained in:
2 files changed
+7
-3
No files matched your search
@@ -131,8 +131,12 @@ registers only from a copy inside `Program Files` that only administrators can c
|
||||
unpack the zip into a folder under `Program Files`. A console run that was not elevated creates the data folder as your
|
||||
own account, and the service then refuses it. Either delete the folder (with SQLite this also deletes the server's
|
||||
database and its accounts), or, before you start the service, give the folder and everything in it to Administrators
|
||||
and reset its permissions from an administrator prompt: `takeown /F "C:\ProgramData\Titano Server" /A /R`, then
|
||||
`icacls "C:\ProgramData\Titano Server" /reset /T`. The server makes the folder private again at its next start.
|
||||
and take your account's access to it away, from a Command Prompt run as administrator under that same account:
|
||||
`takeown /F "C:\ProgramData\Titano Server" /A /R`, then
|
||||
`icacls "C:\ProgramData\Titano Server" /remove:g "%USERDOMAIN%\%USERNAME%" /T`. No other account gains access at any
|
||||
step, and afterwards only SYSTEM and Administrators have it, to the TLS key and `initial-admin-password.txt` too. Do
|
||||
not reset the folder's permissions (`icacls /reset`): everything in it would then inherit those of `C:\ProgramData`,
|
||||
which let every user read it.
|
||||
|
||||
## Translations
|
||||
|
||||
|
||||
+1
-1
@@ -349,7 +349,7 @@ One line per decision: date · decision · alternative · reason.
|
||||
| 2026-10-12 | When another process sharing the archive (a server's admin panel, another PC) changes archive.json, this index catches up when Settings › Archive loads it, before each rescan (desktop and server) and when the server's admin panel opens its archive form. Name, templates and proxy size are registered again from the file without the settings lease. A file that cannot be read, was written by a newer Titano, or belongs to another archive leaves the row alone. The server serves the re-read archive only when the refresh registered a change, and never over an administrator's edit saved since it read the archive (compare-and-swap). | Read the templates from archive.json at every import and upload; refresh only at start | Imports, uploads and the admin panel use the index row, and the admin form saves every field: a stale row lasts only until the next refresh, and an edit made meanwhile registers its own row. |
|
||||
| 2026-10-12 | While the open archive's archive.json cannot be read, Settings › Archive shows the index's templates and proxy size and keeps this PC's thumbnail size, which the index does not store. | Show and save the default thumbnail policy | The stand-in 320 replaced the user's default for new archives whenever the archive was offline. |
|
||||
| 2026-10-12 | An Archive row edited (or Reset section) while the archive at a just-chosen folder is opening waits for that open. The edit then goes to the archive registered at that folder, or stays this PC's default when the folder holds none. An edit made before a later folder change still goes to the folder it was made for, and the rows show the archive at the folder chosen last. | Disable the Archive rows while the folder opens | The edit is neither lost silently nor written into another archive's shared archive.json. Nothing is disabled under the user's typing, where a field losing focus would commit anyway. |
|
||||
| 2026-10-12 | Start with Windows (client and Uploader) shows as on only while Task Manager has not turned the entry off, i.e. its StartupApproved\Run value does not have an odd first byte. The client reads it again when Settings is shown, the Uploader when its settings panel opens. Ticking the box deletes that value, unticking deletes it with the Run value, and re-pointing the command after a rename keeps it. The uninstaller removes only the Run value; a marker left behind is inert. | Read only the Run value; write 0x02 instead of deleting the marker | Task Manager keeps the Run value when it disables an entry, so the box stayed ticked and could not turn the entry back on. With no marker, Windows runs the entry. |
|
||||
| 2026-10-12 | Start with Windows (client and Uploader) shows as on only while Task Manager has not turned the entry off, i.e. its StartupApproved\Run value does not have an odd first byte. The client reads it again when Settings is shown, the Uploader when its settings panel opens. Ticking the box deletes that value, unticking deletes it with the Run value, and re-pointing the command after a rename keeps it. Setup removes the value together with the Run value when it removes the entry (see the Task Manager state row below). | Read only the Run value; write 0x02 instead of deleting the marker | Task Manager keeps the Run value when it disables an entry, so the box stayed ticked and could not turn the entry back on. With no marker, Windows runs the entry. |
|
||||
| 2026-10-12 | A portable copy whose .\data would lie in a folder OneDrive synchronises keeps its data in %LOCALAPPDATA%\Titano. Sync roots come from the OneDrive environment variables and HKCU\Software\Microsoft\OneDrive\Accounts, matched by whole path segments, ignoring case. The copy otherwise stays portable (portable-zip updates, no sign-in entry) and shows a toast at every start (Data kept outside OneDrive, with Open). It then shares the data folder and the single instance with an installed copy of the same user. The Uploader keeps .\data, since its files are JSON written atomically. Other sync tools are not detected. | Refuse to start; a separate per-copy folder under %LOCALAPPDATA%\Titano | BRIEF §6.2 forbids synchronised folders and names the per-user folder as the location. A copy that refused to start would leave the user with nothing. |
|
||||
| 2026-10-12 | The .\data a portable copy now in a OneDrive folder used before (a titano.db or settings.json in it) is left as it is: the log and a toast at every start (Earlier data unused, with Open) name it. Nothing is copied, moved or deleted. | Move or copy it into %LOCALAPPDATA%\Titano at start | Moving an index is a destructive operation (dry-run plan, hash verification, explicit user action), and the per-user folder may already hold an installed copy's index; the user decides which to keep. |
|
||||
| 2026-10-12 | When %LOCALAPPDATA%\Titano itself lies in a OneDrive sync root, the client starts all the same, logs a warning and shows an error toast at every start (Data inside OneDrive, with Open; its tooltip says to exclude the folder from syncing) instead of Data kept outside OneDrive. AppPaths.CreateDirectories, which refuses such a folder, stays unused by the client. | Refuse to start | BRIEF §6.2 names no safer place than the per-user folder; a client that does not start leaves the user nothing, while the warning lets them fix the sync setup. |
|
||||
|
||||
Reference in new issue
Block a user