Remove Ricochet as it is already discontinued in 2016. #476

Closed
ghost wants to merge 1 commits from patch-1 into master
ghost commented 2018-05-29 23:54:33 +00:00 (Migrated from github.com)

Description

The Tor Project said Ricochet is a "Discontinued software" thus it shall be removed.

Software listed here has become depreciated and development has ceased. They are therefore considered unsafe and it is highly recommended to avoid using them. This section is here purely for historical value.
Ricochet IM is an open-source, decentralised instant messenger project that officially ended development in November 2016. Ricochet starts a Tor onion service on the users local system and facilitates communication with other Ricochet users whom are also running their own Ricochet-created Tor onion service, providing End-to-End encryption by never allowing the connection to leave the Tor network.

HTML Preview

Replace [GITHUB_USERNAME] with your GitHub username and [BRANCH] with the branch name.

http://htmlpreview.github.io/?https://github.com/ohmynameisrico/privacytools.io/blob/patch-1/index.html

### Description ## The Tor Project said Ricochet is a "Discontinued software" thus it shall be removed. Software listed here has become depreciated and development has ceased. They are therefore considered unsafe and it is highly recommended to avoid using them. This section is here purely for historical value. Ricochet IM is an open-source, decentralised instant messenger project that officially ended development in November 2016. Ricochet starts a Tor onion service on the users local system and facilitates communication with other Ricochet users whom are also running their own Ricochet-created Tor onion service, providing End-to-End encryption by never allowing the connection to leave the Tor network. ### HTML Preview *Replace [GITHUB_USERNAME] with your GitHub username and [BRANCH] with the branch name.* http://htmlpreview.github.io/?https://github.com/ohmynameisrico/privacytools.io/blob/patch-1/index.html
ghost commented 2018-05-29 23:54:57 +00:00 (Migrated from github.com)
https://github.com/ricochet-im/ricochet/issues/579 https://github.com/privacytoolsIO/privacytools.io/issues/474
hugoncosta commented 2018-08-26 16:11:20 +00:00 (Migrated from github.com)

With the availability of tens of services like this, I guess removing one that doesn't have proper maintenance is a must. @Shifterovich?

With the availability of tens of services like this, I guess removing one that doesn't have proper maintenance is a must. @Shifterovich?
ThatLurker commented 2018-08-26 19:08:52 +00:00 (Migrated from github.com)

what is going to take its place?

what is going to take its place?
hugoncosta commented 2018-08-26 19:16:38 +00:00 (Migrated from github.com)

I'd suggest moving up one of the "Worth Mentioning", such as ChatSecure.

Also, if Richochet is to be removed, the first article of the "Related Information" subsection has to be removed as well.

I'd suggest moving up one of the "Worth Mentioning", such as ChatSecure. Also, if Richochet is to be removed, the first article of the "Related Information" subsection has to be removed as well.
ghost commented 2018-08-26 22:09:27 +00:00 (Migrated from github.com)

Agree, remove. @kewde @beardog108 Which one to replace it with?

Also, if Richochet is to be removed, the first article of the "Related Information" subsection has to be removed as well.

Need a separate PR for that, can't change code in this one.

Agree, remove. @kewde @beardog108 Which one to replace it with? > Also, if Richochet is to be removed, the first article of the "Related Information" subsection has to be removed as well. Need a separate PR for that, can't change code in this one.
ghost commented 2018-08-27 02:13:03 +00:00 (Migrated from github.com)

Its not actually [fully] discontinued. I don't think it should be removed unless someone can show these supposed "10 known vulnerabilities", the Tor wiki page doesn't even mark it as discontinued anymore.

Edit: The 10 vulns were probably referring to it shipping with an outdated Tor binary. You can easily have ricochet use your system binary or replace the one it uses. I suggest we update the site to show a warning for this.

Ricochet is relatively simple, and if it had known unpatched vulnerabilities, the authors would make it clear that its not safe to use.

In addition Ricochet (the protocol anyway) is being extended to support group messaging via the Cwtch project, so development around it is not completely stopped.

Quote From dev on June 4 2018:

I reached out to the author of the Ricochet section on that Tor wiki page and cleared things up. You're free to make judgments about development being stalled, and Ricochet's disclaimers are still in place (experimental, etc), but the "officially ended development" claim was incorrect and is factually false.

IMO Ricochet is just as safe/unsafe as the day of its last release, unless someone can link the vulnerabilities that are claimed to be known. Is it the safest messenger available? No, but it is pretty good, and remember, it did pass the security audit in 2016, which was for the then (and still latest) release.

I wouldn't be upset about moving it to "worth mentioning", since it is clearly not well supported. Tox is alright, but has its own sets of problems and is not as private as Ricochet, although since it is supported, it would be better for the featured spot.

Tl;dr

I suggest moving it to worth mention like suggested, and move Tox to the recommended.

Hopefully one day Ricochet is better supported, as it is simple yet secure (in concept) and anonymous, which is rare.

Its not actually [fully] discontinued. I don't think it should be removed unless someone can show these supposed "10 known vulnerabilities", the Tor wiki page doesn't even mark it as discontinued anymore. Edit: The 10 vulns were probably referring to it shipping with an outdated Tor binary. You can easily have ricochet use your system binary or replace the one it uses. I suggest we update the site to show a warning for this. Ricochet is relatively simple, and if it had *known* unpatched vulnerabilities, the authors would make it clear that its not safe to use. In addition Ricochet (the protocol anyway) is being extended to support group messaging via the [Cwtch project](https://cwtch.im/), so development around it is not completely stopped. Quote From dev on June 4 2018: >I reached out to the author of the Ricochet section on that Tor wiki page and cleared things up. You're free to make judgments about development being stalled, and Ricochet's disclaimers are still in place (experimental, etc), but the "officially ended development" claim was incorrect and is factually false. IMO Ricochet is just as safe/unsafe as the day of its last release, unless someone can link the vulnerabilities that are claimed to be known. Is it the safest messenger available? No, but it is pretty good, and remember, it did pass the security audit in 2016, which was for the then (and still latest) release. I wouldn't be upset about moving it to "worth mentioning", since it is clearly not well supported. Tox is alright, but has its own sets of problems and is not as private as Ricochet, although since it is supported, it would be better for the featured spot. # Tl;dr I suggest moving it to worth mention like suggested, and move Tox to the recommended. Hopefully one day Ricochet is better supported, as it is simple yet secure (in concept) and anonymous, which is rare.
ghost commented 2018-11-13 18:50:27 +00:00 (Migrated from github.com)

As mentioned here https://github.com/privacytoolsIO/privacytools.io/issues/474#issuecomment-438347467 I don't think this should be removed.

I also don't think that "Tox" should be argued as a "replacement" they aren't really the same thing and fundamentally work quite differently.

See:

https://github.com/ricochet-im/ricochet/pull/580#issuecomment-394176462
https://github.com/ricochet-im/ricochet/issues/579#issuecomment-392788611

As mentioned here https://github.com/privacytoolsIO/privacytools.io/issues/474#issuecomment-438347467 I don't think this should be removed. I also don't think that "Tox" should be argued as a "replacement" they aren't really the same thing and fundamentally work quite differently. See: https://github.com/ricochet-im/ricochet/pull/580#issuecomment-394176462 https://github.com/ricochet-im/ricochet/issues/579#issuecomment-392788611
asddsaz commented 2018-11-23 04:12:54 +00:00 (Migrated from github.com)

Without any strong evidence of major security flaws, why should it be deleted?

If you want security with decent ease of use, you use Ricochet. Very few apps come close to it.

Edit: One decent alternative: http://retroshare.net/

Without any strong evidence of major security flaws, why should it be deleted? If you want security with decent ease of use, you use Ricochet. Very few apps come close to it. Edit: One decent alternative: http://retroshare.net/
ghost commented 2018-11-24 05:19:17 +00:00 (Migrated from github.com)

This should be closed along with the duplicate https://github.com/privacytoolsIO/privacytools.io/issues/474

This should be closed along with the duplicate https://github.com/privacytoolsIO/privacytools.io/issues/474
ghost commented 2018-11-24 09:24:50 +00:00 (Migrated from github.com)

They're not duplicates, one is a PR and the other is an issue. But yeah, unless there are legit concerns there's no reason to remove it.

They're not duplicates, one is a PR and the other is an issue. But yeah, unless there are legit concerns there's no reason to remove it.
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#476
No description provided.