Advanced Topics

Repository encryption is disabled

The early encryption experiment did not protect every storage engine or metadata path, so the alpha does not expose it as a security boundary.

Do not rely on repository encryption

Dits does not currently provide complete repository encryption, encrypted remote transport, or supported key management. Protect repositories with operating-system and storage controls appropriate to your environment.

Command behavior

encrypt-init, login, and change-password fail with a nonzero exit status and do not change keystores or repository data.
encrypt-status reports whether a legacy experimental keystore is present. It does not unlock or enable encryption.
logout only clears a legacy on-disk key cache. It does not alter repository contents.

dits encrypt-status
dits logout

Legacy experimental repositories

When a repository contains the old experimental keystore, current repository operations fail closed before loading configuration or storage. This prevents the alpha from silently writing plaintext into a repository that may have been assumed to be protected.

Preserve data before recovery

Do not delete or modify a legacy keystore as a workaround. Preserve a backup of the entire repository and seek project-specific recovery guidance first.

What is planned

A future encryption design needs complete storage coverage, an auditable key lifecycle, migration and recovery semantics, and independent review before it can be presented as a supported security feature. Track this work on the roadmap and review the current security model.