Goals

• Define a common vendor-independent standard for encrypted directories on a per-file basis
• Discuss pros and cons of file formats and cipher choices
• Make the format be as simple as possible and the spec as clear as possible
  • Keep MAY or SHOULD requirements to a minimum to avoid diverging feature sets of different implementations
  • Easier implementation means fewer bugs and incompatibilities
  • Lean on the underlying file system as much as possible
• Create testcases to verify compliance to the format

Non-Goals

• Invent any new ciphers or cryptographic operations
• Define container formats (such as encrypted block devices)
• Create an application

Why?

• Give users freedom of choice regarding their preferred software
• Ease migration between different file encryption applications
• Simplify development and auditing of software

Who is supporting this?

The standardization process is supported by some well-known FOSS products that share the common vision:

• Cryptomator
• Cyberduck
• gocryptfs
• rclone

Contribute

• 📝 Read about of Design Requirements
• 💬 Join our discussions
• 🗣️ Invite other tool vendors to join the effort
• 🩺 Security audits and enhancements are highly welcome 😉