diff --git a/.env.docker b/.env.docker index 9567036..8ffb824 100644 --- a/.env.docker +++ b/.env.docker @@ -5,7 +5,7 @@ /* -------------------------------- Runtime -------------------------------- */ NEXT_PUBLIC_PANEL_NAME=DOKTAINER NEXT_PUBLIC_VERSION=v0.1.0 -NEXT_PUBLIC_BATCH=Batch-20260515 +NEXT_PUBLIC_BATCH=Batch-20260601 NEXT_PUBLIC_API_PORT=4000 # Leave NEXT_PUBLIC_API_URL empty/unset in monolith Docker deployment so the diff --git a/.env.example b/.env.example index 7cf3585..69c3bfd 100644 --- a/.env.example +++ b/.env.example @@ -6,7 +6,7 @@ # Frontend runtime NEXT_PUBLIC_PANEL_NAME=DOKTAINER NEXT_PUBLIC_VERSION=v0.1.0 -NEXT_PUBLIC_BATCH=Batch-20260515 +NEXT_PUBLIC_BATCH=Batch-20260601 # For Docker deployment, leave NEXT_PUBLIC_API_URL unset so the # browser uses same-origin /api/v1 and Next proxies it to the backend. diff --git a/.github/workflows/doktainer-image.yml b/.github/workflows/doktainer-image.yml index 4d15475..0fe998c 100644 --- a/.github/workflows/doktainer-image.yml +++ b/.github/workflows/doktainer-image.yml @@ -117,7 +117,7 @@ jobs: NEXT_PUBLIC_API_PORT=${{ vars.NEXT_PUBLIC_API_PORT || '4000' }} NEXT_PUBLIC_PANEL_NAME=${{ vars.NEXT_PUBLIC_PANEL_NAME || 'DOKTAINER' }} NEXT_PUBLIC_VERSION=${{ github.ref_type == 'tag' && github.ref_name || github.sha }} - NEXT_PUBLIC_BATCH=${{ vars.NEXT_PUBLIC_BATCH || 'Batch-20260515' }} + NEXT_PUBLIC_BATCH=${{ vars.NEXT_PUBLIC_BATCH || 'Batch-20260601' }} - name: Post-push summary if: github.event_name != 'pull_request' diff --git a/Dockerfile b/Dockerfile index 2943b62..d7bc431 100644 --- a/Dockerfile +++ b/Dockerfile @@ -18,7 +18,7 @@ ARG NEXT_PUBLIC_WS_URL= ARG NEXT_PUBLIC_API_PORT=4000 ARG NEXT_PUBLIC_PANEL_NAME=DOKTAINER ARG NEXT_PUBLIC_VERSION=v0.1.0 -ARG NEXT_PUBLIC_BATCH=Batch-20260515 +ARG NEXT_PUBLIC_BATCH=Batch-20260601 ENV NEXT_PUBLIC_API_URL=$NEXT_PUBLIC_API_URL ENV NEXT_PUBLIC_WS_URL=$NEXT_PUBLIC_WS_URL diff --git a/README.id-ID.md b/README.id-ID.md index d384090..5b47a62 100644 --- a/README.id-ID.md +++ b/README.id-ID.md @@ -245,7 +245,7 @@ ENCRYPTION_KEY=replace-this-with-a-secure-32-char-key NEXT_PUBLIC_PANEL_NAME=DOKTAINER NEXT_PUBLIC_VERSION=v0.1.0 -NEXT_PUBLIC_BATCH=Batch-20260515 +NEXT_PUBLIC_BATCH=Batch-20260601 NEXT_PUBLIC_API_PORT=4000 ``` diff --git a/README.md b/README.md index d5b5e41..bf73b34 100644 --- a/README.md +++ b/README.md @@ -245,7 +245,7 @@ ENCRYPTION_KEY=replace-this-with-a-secure-32-char-key NEXT_PUBLIC_PANEL_NAME=DOKTAINER NEXT_PUBLIC_VERSION=v0.1.0 -NEXT_PUBLIC_BATCH=Batch-20260515 +NEXT_PUBLIC_BATCH=Batch-20260601 NEXT_PUBLIC_API_PORT=4000 ``` diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..077e298 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,74 @@ +# Security Policy + +Thank you for helping keep Doktainer and its users secure. + +## Supported Versions + +The following versions currently receive security updates: + +| Version | Supported | +| -------------------------- | --------- | +| Latest Milestone Release | ✅ | +| Previous Milestone Release | ✅ | +| Older Releases | ❌ | + +As Doktainer is currently in the pre-1.0 phase, users are encouraged to always upgrade to the latest available release. + +## Reporting a Vulnerability + +If you discover a security vulnerability, please do **not** create a public GitHub Issue. + +Instead, report the vulnerability privately through: + +- GitHub Security Advisories (preferred) +- GitHub Private Vulnerability Reporting + +Please include: + +- A description of the vulnerability +- Steps to reproduce +- Potential impact +- Suggested mitigation (if available) + +## Response Process + +After receiving a report, the Doktainer maintainers will: + +1. Acknowledge receipt of the report. +2. Investigate and validate the issue. +3. Develop and test a fix. +4. Release a security update if necessary. +5. Publicly disclose the vulnerability after a fix is available. + +## Scope + +Examples of security vulnerabilities include: + +- Authentication bypass +- Privilege escalation +- Remote code execution +- Command injection +- Server-side request forgery (SSRF) +- Sensitive information disclosure +- Container escape vulnerabilities +- Insecure secret handling + +## Disclosure Policy + +Please allow maintainers a reasonable amount of time to investigate and address reported vulnerabilities before publicly disclosing them. + +Responsible disclosure helps protect Doktainer users and infrastructure operators. + +## Security Updates + +Security fixes may be released as maintenance releases: + +- v0.x.1 +- v0.x.2 +- v0.x.3 + +or, when necessary, included in the next milestone release. + +## Acknowledgements + +We appreciate responsible security researchers and community members who help improve the security of Doktainer.