diff --git a/.github/workflows/test-build.yml b/.github/workflows/test-build.yml index a822db14..b1c15c16 100644 --- a/.github/workflows/test-build.yml +++ b/.github/workflows/test-build.yml @@ -84,7 +84,7 @@ jobs: -w /app/backend \ golang@sha256:f86f1a6701e3dcc445fec097a42f78b758f15950ccf032c2d3e54e2754d32fdb `# golang:1.27.1-alpine linux/amd64` \ sh -c "apk add --no-cache gcc musl-dev && go build -trimpath \ - -ldflags='-X github.com/phishingclub/phishingclub/version.hash=ph${{ steps.get_version.outputs.HASH }} -X github.com/phishingclub/phishingclub/version.version=${{ steps.get_version.outputs.VERSION }} -linkmode=external -extldflags=-static' \ + -ldflags='-s -w -X github.com/phishingclub/phishingclub/version.hash=ph${{ steps.get_version.outputs.HASH }} -X github.com/phishingclub/phishingclub/version.version=${{ steps.get_version.outputs.VERSION }} -linkmode=external -extldflags=-static' \ -tags production -o ../build/amd64/phishingclub main.go" # build arm64 binary — run natively under QEMU (already set up above) @@ -97,7 +97,7 @@ jobs: -w /app/backend \ golang@sha256:df4c4a0eeb85873e0122c6e2eb1b436f3131576f572505c1ea61954b00fa6460 `# golang:1.27.1-alpine linux/arm64` \ sh -c "apk add --no-cache gcc musl-dev && go build -trimpath \ - -ldflags='-X github.com/phishingclub/phishingclub/version.hash=ph${{ steps.get_version.outputs.HASH }} -X github.com/phishingclub/phishingclub/version.version=${{ steps.get_version.outputs.VERSION }} -linkmode=external -extldflags=-static' \ + -ldflags='-s -w -X github.com/phishingclub/phishingclub/version.hash=ph${{ steps.get_version.outputs.HASH }} -X github.com/phishingclub/phishingclub/version.version=${{ steps.get_version.outputs.VERSION }} -linkmode=external -extldflags=-static' \ -tags production -o ../build/arm64/phishingclub main.go" else echo "BUILD_ARM not enabled - skipping arm64 build" diff --git a/README.md b/README.md index 3e3c85f4..71def9e8 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ Phishing Club provides a lot of features for simulation and red teaming, such as - **Awareness training** - Run training campaigns that record started and completed, kept separate from phishing risk - **Campaign reports** - PDF export with customizable HTML templates for phishing and training, automatically emailed on completion - **Analytics** - Timelines, dashboards, per-user event history -- **Automation** - HMAC-signed webhooks, REST API, import/export +- **Automation** - HMAC-signed webhooks, REST API and embedded JavaScript scripting engine - **Multi-tenancy** - Segregated client handling and statistics for service providers - **Anonymization** - Pseudonymized campaigns, automatic anonymization on close and retention windows for compliance - **Branding** - Replace logos and login image with your own @@ -104,22 +104,13 @@ For prerequisites, service ports, make commands, local DNS and SSL setup, see [D ## License -Phishing Club is available under a dual licensing model: - -### Open Source License (AGPL-3.0) This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). This means: - ✅ You can use, modify, and distribute the software freely - ✅ Perfect for educational, research, and commercial use - ✅ You can run your own instance for security testing or professional services - ⚠️ **Important**: If you provide the software modified as a network service, you must make your source code available under AGPL-3.0 -### Commercial License -For organizations that want to: -- Use Phishing Club in commercial products without AGPL restrictions -- Offer Phishing Club as a service without source code disclosure -- Modify the codebase without source code disclosure - -**Contact for commercial licensing**: [license@phishing.club](mailto:license@phishing.club) +**Contact reqarding license**: [license@phishing.club](mailto:license@phishing.club) ## Roadmap