Repository navigation
v0.10.0
Highlights
Accounts and administration
- Public sign-up, under your control. Admins can open sign-up from Admin → System → Authentication. New accounts confirm their email and wait for an admin to approve them. Sign-up is closed by default.
- Mail server settings. Configure SMTP under Admin → System → Mail server, with presets for Resend, SendGrid, Postmark, Mailgun, Amazon SES, Brevo and Gmail, and send a test email.
- User presence. Admins can see who is online and when each user was last active.
Security
- Encryption. Stored credentials use authenticated AES-256-GCM tied to their key. Existing data is re-encrypted with your key at boot, and rotating keys is now safe.
- Required secrets. Deployments need
ENCRYPTION_KEYSandBETTER_AUTH_SECRET, so no stack runs on public default secrets anymore. - Tighter access.
- The workspace comes only from the
X-Workspace-Idheader. - Worker file downloads are authenticated and confined to tool archives.
- An unused stream endpoint without session authorization was removed.
- The workspace comes only from the
- External links. External links in the console ask before they open.
Security agent
- Specialist subagents for reconnaissance, web, network and validation, with wider fan-out and short-term memory.
- Skills. New builtin skills for API testing and for OSINT and assets, and rewritten pentest skills that explain how, not just what.
- Run control.
- Stop cancels subagents too.
- A run can resume midway.
- Plans can require approval.
- Results and browser sessions. Subagent results reach the main agent without polling, and the Browser tab shows every browser session.
Workspace files
- Per-workspace file storage with sharing by email or public link, under a storage quota. Agents save their output files there.
Performance and polish
- Faster API. Sessions are resolved from Redis, and the API runs on Node's HTTP adapter instead of Express.
- Notifications load page by page with infinite scroll and can be marked read or unread.
- Dashboard. Counts are consistent, the security score runs from 0 to 100, and the queries are lighter.
Upgrade notes: read before upgrading
v0.10.0 hardens how secrets are handled. core-api will not start until these are set in .env:
| Variable | Value |
|---|---|
ENCRYPTION_KEYS |
Random, 32+ characters: openssl rand -base64 32. Back it up. Losing it loses every stored credential |
BETTER_AUTH_SECRET |
Another openssl rand -base64 32 value. Signs sessions and email verification links |
BASE_URL (recommended) |
Public URL of the console, origin only (e.g. https://oasm.example.com). Used for email verification links and the Telegram webhook |
Steps
- Back up PostgreSQL. On its first successful start, v0.10.0 re-encrypts stored credentials in a format v0.9 cannot read, so restoring the backup is the only way back.
- Set
ENCRYPTION_KEYS. First check which key your data uses:docker exec oasm-api printenv ENCRYPTION_KEYS- Empty. This is every oasm-docker stack until now, whatever
.envsaid. Set a new key; data under the built-in default key stays readable. - A random value of 32+ characters. Keep it.
- A short or example value. Keep it first and add a new key after it:
ENCRYPTION_KEYS=<current key>,<new key>.
- Empty. This is every oasm-docker stack until now, whatever
- Set
BETTER_AUTH_SECRET, andBASE_URLif the stack is reachable from outside. - Update. With oasm-docker, run
make update. It pulls the compose file that passes these values tocore-api(oasm-platform/oasm-docker#4) and the new images. Migrations run automatically. - Check the log. Run
docker compose logs core-api | grep -i secretand expect "Re-encrypted with the active key …", then "Every stored secret now uses the active key".
If a value is missing, core-api exits at start with a message naming it, before it touches any data. Set it and start again.
Full guide: https://docs.oasm.io/deployment#updates
What changes for users
- Everyone signs in again once, because of the new session secret.
- Public sign-up is closed by default. Admins can open it under Admin → System → Authentication once Admin → System → Mail server works. New accounts confirm their email and wait for an admin to approve them. Existing accounts, and accounts created by admins, are not affected.
- API clients send the workspace in the
X-Workspace-Idheader. AworkspaceIdquery parameter is no longer accepted, andDELETE /api/targets/:id/workspace/:workspaceIdis nowDELETE /api/targets/:id. - The first page load opens the first workspace, because no selection has been stored yet.
- Workers from v0.9.x keep working.
Security fixes in this release
- Stored credentials were effectively unprotected on oasm-docker stacks. The compose file never passed
ENCRYPTION_KEYS, so credentials were encrypted with the built-in default key. After you set a key, they are re-encrypted with it (#809, #810). - Rotation could return wrong values. After a key rotation, about 0.4% of decrypts returned another value without an error. New data uses authenticated AES-256-GCM (#809).
- Sessions were signed with a public default. Without
BETTER_AUTH_SECRET, sessions and verification links were signed with a publicly known secret; it is now required (#811).
Changelog
Features
- a088ea9: feat(notifications): cursor pagination, infinite scroll and read toggles (#781) (@l1ttps)
- 2d60720: feat(admin): show users' online status and last activity (#789) (@l1ttps)
- 0893d27: feat(agents): add api-testing and osint-and-assets builtin skills (#790) (@l1ttps)
- dced3c7: feat(agents): add specialist subagents for recon, web, network and validation (#793) (@l1ttps)
- 59b3a06: feat(agents): widen subagent fan-out and give subagents short-term memory (#794) (@l1ttps)
- 8068813: feat(artifacts): workspace file storage with sharing and quota (#771) (@mizhm)
- bc3b5f0: feat(agents): stop cancels subagents, resume mid-run, approval-gated plans (#798) (@l1ttps)
- fb5a499: feat(agents): update issue creation titles in bug and feature report workflows (@l1ttps)
- c65800d: feat(agents): hand subagent results to the next step and show every browser session (#805) (@l1ttps)
- 4ca4b33: feat(console): confirm before opening external links (#807) (@l1ttps)
- 3d2ec9d: feat(core-api): re-encrypt stored secrets with the active key at boot (#810) (@l1ttps)
- 668e356: feat(auth): system settings, gated sign-up with approval and email verification (#811) (@l1ttps)
Bug fixes
- 1bde75f: fix(remote-execute): remove unused stream endpoint lacking session authorization (#780) (@mizhm)
- eed3c7a: fix(core-api): take the workspace from the header, never from query params (#784) (@l1ttps)
- 17bf362: fix(dashboard): consistent open counts, 0-100 security score and lighter queries (#785) (@l1ttps)
- d442a0f: fix(core-api): guard and confine the worker tool archive gRPC (#808) (@mizhm)
- da7583d: fix(core-api): authenticated encryption that survives key rotation (#809) (@l1ttps)
Refactor
- 28b6aad: refactor(agents): strengthen the builtin pentest skills (#791) (@l1ttps)
- e222433: refactor(agents): make agent mode orchestrate instead of testing (#792) (@l1ttps)
Others
- 01d1cc6: perf(notifications): patch cached pages instead of refetching after mutations (#782) (@l1ttps)
- ccdb237: perf(auth): Redis session cache and consistent login, logout and workspace switching (#783) (@l1ttps)
- e408c4d: perf(core-api): run on the Node HTTP adapter instead of Express (#786) (@l1ttps)