🆕 Software Suggestion | Toffeeshare #1650

Closed
opened 2020-01-11 22:13:05 +00:00 by wuniversales · 4 comments
wuniversales commented 2020-01-11 22:13:05 +00:00 (Migrated from github.com)

Name: Toffeeshare
Category: Share files (P2P)
URL: https://toffeeshare.com/

Use p2p technology to share the files.
No size limit.
Encrypted
Pretty easy to use.

Name: Toffeeshare Category: Share files (P2P) URL: https://toffeeshare.com/ Use p2p technology to share the files. No size limit. Encrypted Pretty easy to use.
Mikaela commented 2020-01-11 22:33:45 +00:00 (Migrated from github.com)

And what makes them better or worth mentioning compared to our current file sharing section?

And what makes them better or worth mentioning compared to our current file sharing section?
wuniversales commented 2020-01-12 00:29:58 +00:00 (Migrated from github.com)

It's p2p, sent from the web, encrypted point to point, I think it's worth mentioning.

It's p2p, sent from the web, encrypted point to point, I think it's worth mentioning.
LukeSeers commented 2020-01-15 15:35:19 +00:00 (Migrated from github.com)

What I have discovered:

Their DNS points to wolfined.com
ns1.wolfined.com
ns2.wolfined.com

From going by their logo "Development & Hosting" I'm going to assume that they are the ones who have made toffeeshare.com.

Also: in their contact details on wolfined.com/contact they are from The Netherlands while also ToffeeShare is in the The Netherlands twitter.com/ShareToffee

What puts me off:

  1. They are not open source.
  2. When they say "End-to-End encrypted" that is very vague. That is a trick which most companies use to make the product seem more secure. Since the users think that their information is encrypted on there servers, which in most cases they are not talking about that. They are talking about the connection from you to their servers which is also known as HTTPS.
  3. "Peer to peer" that is really up for debate. If you understand how p2p works you would know that a user would need to connect to their server first to be able to connect to the other user directly. But since it's not open source we can not verify as easily if it is even p2p. One way is to check the connection between 2 users, but thats too much effort for me.

If they was todo zero-knowledge and they was open source I would maybe would give them a shot.

I thought I would chip in. I recommend double checking my research and coming to your own conclusion because we are human after all :)

### What I have discovered: Their DNS points to [wolfined.com](https://wolfined.com) `ns1.wolfined.com` `ns2.wolfined.com` From going by their logo "Development & Hosting" I'm going to assume that they are the ones who have made [toffeeshare.com](https://toffeeshare.com/). Also: in their contact details on [wolfined.com/contact](https://wolfined.com/contact) they are from **The Netherlands** while also ToffeeShare is in the **The Netherlands** [twitter.com/ShareToffee](https://twitter.com/ShareToffee) ### What puts me off: 1. They are not open source. 2. When they say "End-to-End encrypted" that is very vague. That is a trick which most companies use to make the product seem more secure. Since the users think that their information is encrypted on there servers, which in most cases they are not talking about that. They are talking about the connection from you to their servers which is also known as **HTTPS**. 3. "Peer to peer" that is really up for debate. If you understand how p2p works you would know that a user would need to connect to their server first to be able to connect to the other user directly. But since it's not open source we can not verify as easily if it is even p2p. One way is to check the connection between 2 users, but thats too much effort for me. If they was todo **zero-knowledge** and they was **open source** I would maybe would give them a shot. I thought I would chip in. I recommend double checking my research and coming to your own conclusion because we are human after all :)
Mikaela commented 2020-01-15 16:11:03 +00:00 (Migrated from github.com)

Thank you for your comment @LukeSeers, I am not able to find the source code either and as there are (better) open source options for file sharing I am closing this issue.

Thank you for your comment @LukeSeers, I am not able to find the source code either and as there are (better) open source options for file sharing I am closing this issue.
This repo is archived. You cannot comment on issues.
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#1650
No description provided.