Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.
Security Policy
DBBASIC Object Server is being extracted from a working private prototype in small, reviewed public commits.
Security work is part of the product, not an afterthought. The runtime executes Python objects, persists state/logs/versions, exposes HTTP endpoints, and will support tools such as DBBASIC Scroll. Treat changes to execution, authentication, authorization, persistence, file access, source editing, logs, and deployment as security-sensitive.
Supported Versions
This repository is pre-release. There are no supported production versions yet.
Public commits should still be reviewed as if they may become part of the production runtime.
Reporting Security Issues
Please do not open a public issue that includes:
- live deployment hostnames or IP addresses
- credentials, API keys, tokens, cookies, or private URLs
- exploit details that would enable immediate abuse
- private object source, state, logs, files, or customer data
Send security reports to:
dan@askrobots.com
Use a concise subject such as:
Security report: dbbasic-object-server
Include enough information to reproduce the issue safely with local or placeholder configuration.
Public Sample Values
Use only safe placeholder values in public reports, code, tests, and documentation:
127.0.0.1for localhost samples192.0.2.0/24,198.51.100.0/24, or203.0.113.0/24for documentation IPsexample.com,example.net, orexample.orgfor documentation domains
Do not include real LAN IPs, cloud IPs, customer hostnames, private station names, filesystem paths, tokens, or secrets.
Security-Sensitive Areas
Review these areas carefully before merging changes:
- object execution
- source loading and import restrictions
- permissions and row filters
- authentication and session handling
- state, log, file, and version storage
- queue, scheduler, and event processing
- external callbacks and webhooks
- cluster/station communication
- backup, restore, and migration paths
- DBBASIC Scroll access to source, state, logs, files, and versions
Public Staging Rules
The current public server is useful for staging and dogfooding, but it is not a general-purpose public code execution platform yet.
For public staging:
- bind uvicorn to
127.0.0.1 - put Caddy or another reverse proxy in front
- proxy only explicit public object routes
- keep
DBBASIC_ENABLE_SOURCE_WRITES=false - generate a deployment-specific
DBBASIC_ADMIN_TOKENfor local/admin introspection - do not expose source, version, logs, state, metadata, or object-list routes to
normal users until role and object permissions are enforced
- do not add a public object-create route until permissions are enforced
With this shape, outside users can run only the objects intentionally exposed by the proxy. They cannot add, edit, roll back, list, or inspect arbitrary objects through the public hostname.
The current public ASGI server now enforces an admin-token gate for object listing and introspection reads. Treat that as a temporary admin-only control, not as the final permissions model.
Current Status
The public repository currently contains a minimal ASGI server, direct Python object loader, object namespace resolution, source update and rollback gates, state/log/version storage, a daemon slice, tests, and a single-VM staging guide.
Object listing and introspection reads require an admin token. Source update and rollback routes are disabled by default and require both DBBASIC_ENABLE_SOURCE_WRITES=true and an admin token when enabled. This is a temporary development gate, not the final authorization system.
Do not assume this repository is production-ready until the runtime, permissions, execution boundaries, and deployment process are documented and tested.