Security considerations #60
Conversation
|
|
||
| Privacy for Whisper / Waku haven't been studied rigorously for various threat models like global passive adversary, local active attacker, etc. This is unlike e.g. Tor and mixnets. | ||
|
|
||
| **Topic hygiene:** |
There was a problem hiding this comment.
I'm not sure this needs to be a separate section. As, in theory, this only applies when you are a light node or when you are connecting with a mailserver (and in v1 when you are a Waku client).
In the other scenarios this should be fine as peers will not know who a message comes from, or is intended for.
It is different for bloom filter as peers specifically broadcast their filter setting.
There was a problem hiding this comment.
Hm, where would you put it? Something like this:
If you use a very specific topic you reveal more information.
under light client privacy?
There was a problem hiding this comment.
@cammellos @adambabik wdyt
There was a problem hiding this comment.
Yeah, I don't know. I guess it can stay there
oskarth
force-pushed
the
security-considerations
branch
from
3952251 to
a77c1ef
Compare
oskarth
force-pushed
the
security-considerations
branch
from
a77c1ef to
903c1b1
Compare
Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com>
Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com>
* Initial cut * scalability ux section * moar * version and toc * fix port * clarify bloom * update bw usage link to version controlled * remove mvds refer * Update waku.md Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com> * Update waku.md Co-Authored-By: Dean Eigenmann <dean.eigenmann@icloud.com>
Addresses #39