Files

David Helkowski 833ae4fe72 Add encryption export compliance documentation for macOS build

This commit introduces two new files: EXPORT_COMPLIANCE.filled.txt and EXPORT_COMPLIANCE.pdf, detailing the encryption export compliance statement for the Strawberry app. The text file outlines the app's use of encryption, confirming it qualifies for exemption under U.S. export regulations. The PDF provides a formatted version of the same information, ensuring compliance documentation is readily available for developers and reviewers.

2026-01-22 20:42:59 +09:00

EXPORT_COMPLIANCE.filled.txt

Add encryption export compliance documentation for macOS build

2026-01-22 20:42:59 +09:00

EXPORT_COMPLIANCE.pdf

Add encryption export compliance documentation for macOS build

2026-01-22 20:42:59 +09:00

EXPORT_COMPLIANCE.txt

Implement Mac App Store build support by introducing the BUILD_FOR_MAC_APP_STORE option. This change disables Sparkle and localhost OAuth redirect server for MAS builds, updates CMake configuration, and modifies build scripts accordingly. Additionally, the macOS bundle identifier is now configurable via CMake.

2026-01-22 19:28:00 +09:00

make_pdf.sh

Refactor PDF generation in make_pdf.sh to streamline the process by removing reliance on textutil. The script now directly converts plain text to PDF using cupsfilter, enhancing compatibility and reducing complexity.

2026-01-22 19:29:59 +09:00

README.md

2026-01-22 19:29:59 +09:00

README.md

Export compliance (encryption)

Apple may require an "Export Compliance" statement upload when submitting to the Mac App Store.

This folder contains:

EXPORT_COMPLIANCE.txt: a template statement (fill-in placeholders)
make_pdf.sh: a helper to fill the template and generate a PDF you can upload

Generate the PDF

From the repo root:

./build_tools/macos/export_compliance/make_pdf.sh \
  --bundle-id com.dryark.strawberry \
  --version 1.2.3 \
  --developer "Dry Ark LLC" \
  --contact "support@example.com"

Outputs:

build_tools/macos/export_compliance/EXPORT_COMPLIANCE.filled.txt
build_tools/macos/export_compliance/EXPORT_COMPLIANCE.pdf

Important

This template assumes the app uses only standard OS-provided encryption (e.g. TLS/HTTPS via system frameworks) and does not ship proprietary or standalone crypto libraries.

If you bundle your own crypto library (e.g. OpenSSL) or implement custom encryption, you likely need different answers/documentation.