Security Hardening

This page is about reducing operational risk in real deployments.

1. Rotate every generated token

Never keep default generated values for:

Treat them as shared secrets.

Do not publish every transport just because it exists.

Examples:

Prefer:

when the consumer is on the same machine.

Use 0.0.0.0 only when remote access is actually required.

Allow only what you need:

Do not open transport ports broadly if the integrating node is known and fixed.

Use different:

for production, staging, and local testing.

If GeyserVoice manages the VoiceCraft runtime:

This is not a normal hardening feature.

It is primarily for:

Blindly disabling packet types can break auth, sync, or audio.

For GeyserVoice, keep these staff-only:

Backups may contain:

Treat config backups as sensitive operational data.