Skip to content

add E2EE to official Nextcloud documentation #936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gerbrent opened this issue Mar 5, 2025 · 1 comment · May be fixed by nextcloud/documentation#12821
Open

add E2EE to official Nextcloud documentation #936

gerbrent opened this issue Mar 5, 2025 · 1 comment · May be fixed by nextcloud/documentation#12821
Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. enhancement New feature or request

Comments

@gerbrent
Copy link

gerbrent commented Mar 5, 2025

Is your feature request related to a problem? Please describe.
Searching the Nextcloud Documentation does not give any results for E2EE, only server-side encryption in both the User and Admin docs:

Encrypting your Nextcloud files on the server — Nextcloud latest User Manual latest documentation
Encryption configuration — Nextcloud latest Administration Manual latest documentation

Describe the solution you'd like
Add E2EE to the official documentation!
The README here is a great starting point. Would be great to add this to the official documentation for easier discovery.

Describe alternatives you've considered

Additional context

@gerbrent gerbrent added 0. Needs triage Pending approval or rejection. This issue is pending approval. enhancement New feature or request labels Mar 5, 2025
@artonge
Copy link
Collaborator

artonge commented Mar 18, 2025

@gerbrent Feel free to give feedback on nextcloud/documentation#12821 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants