You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
The problem is that currently there is no method to ensure the integrity of the contentTopic and timestamp fields of waku messages. As such, an adversarial node can tamper with these fields without being caught. This can be exploited for censorship, e.g., the attacker can make the message unavailable by changing its timestamp to a time in the past. Similarly, the adversary may amend the contentTopic and make it unreachable to the intended peers. The adversarial peer can be a relay node or a store node.
Acceptance Criteria
Investigate the potential attacks related to this issue
To sketch out potential solutions
The text was updated successfully, but these errors were encountered:
staheri14
changed the title
14/WAKU2-MESSAGE: Lack of integrity for contentTopic and `timestamp in waku messages
14/WAKU2-MESSAGE: Lack of integrity for contentTopic and timestamp in waku messages
Aug 6, 2021
Problem
The problem is that currently there is no method to ensure the integrity of the
contentTopic
andtimestamp
fields of waku messages. As such, an adversarial node can tamper with these fields without being caught. This can be exploited for censorship, e.g., the attacker can make the message unavailable by changing itstimestamp
to a time in the past. Similarly, the adversary may amend thecontentTopic
and make it unreachable to the intended peers. The adversarial peer can be a relay node or a store node.Acceptance Criteria
The text was updated successfully, but these errors were encountered: