The owner renamed the product and moved the repository to the self-hosted Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control, and asked for Actions and a first automatic release with the server package and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md). - Chronos everywhere: a byte-exact rename of contents and paths, then a per-language review of the forms the old name's ending had dictated. - Gitea instead of GitHub: the update check, licence, issue and support links read ChronosReleasesUrl; the update check takes the highest stable version, offers a pre-release build its final release and reports a repository it cannot see as a failed check. EULA, security policy and Gitea issue forms live at the repository root. - Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release, nightly image and performance gates in the .NET SDK container with git checkout and the system SQLite. The release cross-compiles the Windows programs, checks their icon, version and DPI manifest, packs installers and zips, publishes the Gitea release and pushes the server image (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows runner (WINDOWS_RUNNER). - New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the docker-exec script, which Gitea's service containers do not allow; the throw-away server runs without durability) and pe-check. - Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR, 3 on the shared runner; the weekly performance gates keep theirs). BREAKING CHANGE: programs, settings, data folders, file types, environment variables and the Docker image use the new name; nothing is migrated from Titano, which never had a release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2.5 KiB
Security policy
Supported versions
Security fixes are made for the latest release only. Upgrade before reporting a problem you found in an older
version; the in-app update check (Settings › Updates) and docker compose pull keep installations current.
| Version | Supported |
|---|---|
| Latest release | Yes |
Older releases, pre-releases, :nightly images |
No |
Reporting a vulnerability
Please do not open a public issue for a security problem.
Gitea has no private vulnerability reporting: report the problem privately to the maintainers, through the contact on the repository owner's Gitea profile or by e-mail to them. Include:
- the affected program (Chronos, Uploader, Server) and version (About, or
/api/v1/server/infofor the server); - how to reproduce the problem, and what an attacker gains;
- whether the server runs behind a reverse proxy and which TLS mode it uses (
auto,pem,proxy).
Do not attach diagnostics bundles or logs that you have not read: they are scrubbed of passwords and tokens, but they contain host names, folder paths and user names.
You will receive an acknowledgement within 7 days. Fixes are released as soon as they are ready, and the release notes credit the reporter unless they prefer otherwise. Please give us 90 days, or until a fix is released, before disclosing the problem publicly.
Scope
In scope: the desktop programs, the installer, the server API and admin panel, the Docker image and the Unraid template published here.
Out of scope: problems that need an attacker who already controls the user's Windows account or the server host; denial of service through unrealistic load; self-signed certificate warnings (the client pins the fingerprint you confirm at first connection); findings from automated scanners without a demonstrated impact.
How Chronos protects you
- Releases list the SHA-256 of every file in
SHA256SUMS; the in-app update download refuses a file whose hash does not match. Builds are Authenticode-signed when a signing certificate is configured. - The server stores passwords with PBKDF2-SHA512 (210,000 iterations) and session tokens only as SHA-256 hashes; sign-in is rate limited and accounts lock after repeated failures.
- Desktop clients pin the server certificate fingerprint on first use, never send a saved token to a server whose certificate changed, and keep tokens encrypted with Windows DPAPI.
- No program runs external tools or scripts; the only programs Chronos starts are your browser (for links) and Explorer (to show a folder).