Security policy¶
How to report a vulnerability in Dinatos, and a summary of its security design.
Supported versions¶
Dinatos is pre-1.0 (0.x). Only the latest release and main receive security fixes. Reproduce on the latest release before reporting.
Report a vulnerability¶
Do not open a public issue or pull request.
Go to the repository’s Security tab.
Choose Report a vulnerability, or open https://github.com/bergercookie/dinatos/security/advisories/new.
Include the affected version or commit, how you deploy it (Docker image or native client), steps to reproduce, and the impact.
What to expect¶
One individual maintains Dinatos. These are good-faith targets, not guarantees:
Acknowledgement within about a week.
A follow-up once the issue is confirmed or ruled out.
A fix in a new release for confirmed issues, with credit in the advisory if you want it.
Please allow time for a fix before public disclosure.
Security design¶
Area |
Behaviour |
|---|---|
Sessions |
|
Logout |
|
Lifetime |
30 days by default ( |
Passwords |
Hashed with Argon2. Never stored in the clear. |
Registration |
Open by default. An administrator turns it off in Settings -> Administration. If the operator sets |
MCP endpoint |
|
API keys |
|
Cookies and CORS |
Auth uses an |
For operators: see Security and networking.