Ora Browser uses Ed25519 cryptographic keys to sign and verify app updates for security.

• File: ora_public_key.pem
• Purpose: Verifies update signatures in the app
• Status: 4BDC Committed to git repository
• Safety: Public keys are safe to share

• File: .env (contains ORA_PRIVATE_KEY)
• Purpose: Signs app updates during release
• Status: Never committed to git
• Safety: Keep secure and private

1. First machine: Keys auto-generated and saved appropriately
2. Additional machines: Copy .env file from first machine
3. Release process: ./create-release.sh handles key management automatically

• .env is in .gitignore - it will never be committed
• Public key is committed - this is safe and required
• Never share your private key with anyone
• If private key is lost, you'll need to regenerate keys (breaks update chain)

Run ./check-security.sh to verify:

• Private key exists but is not tracked by git
• Public key is available for app integration
• .gitignore properly excludes sensitive files

• NEVER commit private keys to version control
• NEVER share private keys with anyone
• NEVER delete private keys once you've published releases (breaks update chain)
• Use secure methods to transfer keys between machines
• Regularly audit what's in your git staging area before committing

If you see any of these, stop immediately:

• Private key files appear in git status
• Private keys are committed to repository
• Private keys are shared or transmitted insecurely