privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

📝 Correction | Nextcloud's end to end encryption is now production ready. #2054

New Issue
Closed
opened 2020-09-17 19:48:51 +00:00 by ghost · 3 comments
ghost commented 2020-09-17 19:48:51 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Description

On the privacytools.io website next to Nextcloud (in the self-hosted cloud server section), there is a warning saying that nextcloud's end to end encryption is still in an "alpha state" (hover over the Experimental E2EE flag). However, in a recent announcement by nextcloud, they said that end to end encryption is now production ready.

https://nextcloud.com/blog/production-ready-end-to-end-encryption-and-new-user-interface-arrive-with-nextcloud-desktop-client-3-0/

Why I am making the suggestion

I am making this suggestion as an update to status of Nextcloud on the privacytools.io website.

My connection with the software

I am just a user, not affiliated with the company in any way.

  • [X ] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## Description On the privacytools.io website next to Nextcloud (in the self-hosted cloud server section), there is a warning saying that nextcloud's end to end encryption is still in an "alpha state" (hover over the Experimental E2EE flag). However, in a recent announcement by nextcloud, they said that end to end encryption is now production ready. https://nextcloud.com/blog/production-ready-end-to-end-encryption-and-new-user-interface-arrive-with-nextcloud-desktop-client-3-0/ ## Why I am making the suggestion I am making this suggestion as an update to status of Nextcloud on the privacytools.io website. ## My connection with the software I am just a user, not affiliated with the company in any way. - [X ] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
🎉 3
ghost commented 2020-09-19 11:49:21 +00:00 (Migrated from github.com)
Copy Link
Copy Source

they said that end to end encryption is now production ready.

By their words, yes. But, if you will look at they opened issues and at the forum, you will find a lot of bugs and unsolved issues.

Well, technically, we need to mark it as "production ready". But everyone must think twice before using it (Of course, if you do not want to spend the rest of your time recovering your files and fixing bugs.). E2EE is still a nightmare... Maybe not in alpga stage, but still an unfinished work.

> they said that end to end encryption is now production ready. By their words, yes. But, if you will look at they opened issues and at the forum, you will find a lot of bugs and unsolved issues. Well, technically, we need to mark it as "production ready". But everyone must think twice before using it (Of course, if you do not want to spend the rest of your time recovering your files and fixing bugs.). E2EE is still a nightmare... Maybe not in alpga stage, but still an unfinished work.
lynn-stephenson commented 2020-09-21 00:54:54 +00:00 (Migrated from github.com)
Copy Link
Copy Source

I will take a look at the E2EE module soon; see what known issues are open/not-resolved, and look at their implementations on clients.

Definitely doesn't feel production ready.

I will take a look at the E2EE module soon; see what known issues are open/not-resolved, and look at their implementations on clients. Definitely doesn't feel production ready.
ghost commented 2020-09-21 15:03:29 +00:00 (Migrated from github.com)
Copy Link
Copy Source

That's not the point. They announced that it is production ready, so the tag that says that e2ee is still in "alpha" should be changed. Since they announced it was production ready, it should not be called "alpha" software.

Thank you for taking the time to review the issues and code.

That's not the point. They announced that it is production ready, so the tag that says that e2ee is still in "alpha" should be changed. Since they announced it was production ready, it should not be called "alpha" software. Thank you for taking the time to review the issues and code.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
:mag:🤖 Search Engines
I2P
The Invisible Internet Project (I2P)
 OS
Operating Systems
 Self-contained networks
Social media
Tor
Anything covering the Tor network
 WIP
active work in progress, do not merge or PR (yet)!
 XMPP
Extensible Messaging and Presence Protocol
 [m]
Matrix protocol
 approved
approved, waiting for a PR
 dependencies
Pull requests that update a dependency file
 duplicate
feedback wanted
high priority
iOS
low priority
stale
A label for stalebot if it gets added
 streaming
Anything related to media streaming.
 todo
wontfix
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
 ₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
Browser Extension related issues
 ✨ enhancement
❌ software removal
🆕 software suggestion
🆘 critical
🇦🇶 translations
Anything covering a translated version of the site
 🌐 Social News Aggregators
🌐 hosting
🌐 website issue
*Technical* issues with the website.
 🏠 housekeeping
Anything primarily related to site cleanup.
 🐛 bug
👁️ browsers
👥 team chat
💢 conflicting
💬 discussion
💻 hardware
📁 file storage
📝 correction
Correction of content on the website
 📧 email
🔎 research required
🔐 password managers
🔒 VPN
Virtual Private Network
 🔒 file encryption
🖊️ digital notebooks
🗄️ DNS
Domain Name System
 🗨️ instant messaging (im)
🚫 Windows
🤖 Android
🦊 Firefox
Firefox & forks, about:config etc.
 🧰 productivity tools
No labels 📝 correction
Milestone
No items
No Milestone
Assignees
Clear assignees
jonah
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#2054