vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarification about mailserver trust requirement (#450) 

* clarification about mailservers trust assumption

* some revisions

* ID/IP

* minor fix

* updates mail server security considerations
This commit is contained in:
Sanaz Taheri Boshrooyeh 2021-08-11 12:22:27 -07:00 committed by GitHub
parent 7cd14d049b
commit 6f5eae0d12
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/docs/rfcs/6/README.md
View File

@ -472,7 +472,15 @@ Waku currently lacks incentives to run nodes, which means node operators are mor
#### Light node privacy: #### Light node privacy:
The main privacy concern with light nodes is that directly connected peers will know that an envelope originates from them (as it are the only ones it sends). This means nodes can make assumptions about what envelopes (topics) their peers are interested in. The main privacy concern with a light node is that it has to reveal its topic interests (in addition to its IP/ID) to its directed peers. This is because when a light node publishes an envelope, its directed peers will know that the light node owns that envelope (as light nodes do not relay other envelopes). Therefore, the directed peers of a light node can make assumptions about what envelopes (topics) the light node is interested in.
#### Mailserver client privacy:
A mailserver client fetches archival envelopes from a mailserver through a direct connection.
In this direct connection, the client discloses its IP/ID as well as the topics/ bloom filter it is interested in to the mailserver.
The collection of such information allows the mailserver to link clients' IP/IDs to their topic interests and build a profile for each client over time.
As such, the mailserver client has to trust the mailserver with this level of information.
#### Bloom filter privacy: #### Bloom filter privacy:

6
content/docs/rfcs/8/README.md
View File

@ -96,7 +96,11 @@ A mailserver has to be online to receive envelopes for other nodes, this puts a
**Mailserver client privacy:** **Mailserver client privacy:**
A mailserver client has to trust a mailserver, which means they can send direct traffic. This reveals what topics / bloom filter a node is interested in, along with its peerID (with IP). A mailserver client fetches archival envelopes from a mailserver through a direct connection.
In this direct connection, the client discloses its IP/ID as well as the topics/ bloom filter it is interested in to the mailserver.
The collection of such information allows the mailserver to link clients' IP/IDs to their topic interests and build a profile for each client over time.
As such, the mailserver client has to trust the mailserver with this level of information.
A similar concern exists for the light nodes and their direct peers which is discussed in the security considerations of [6/WAKU1](/spec/7).
**Mailserver trusted connection:** **Mailserver trusted connection:**