Waku message security considerations (#280)

* adds security consideration

* removes the waku version for the security consideration
This commit is contained in:
Sanaz Taheri Boshrooyeh 2020-12-21 11:25:52 -08:00 committed by GitHub
parent 01f279893e
commit c030ee6920
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -2,7 +2,7 @@
title: Waku Message
version: 2.0.0-beta1
status: Draft
authors: Oskar Thorén <oskar@status.im>
authors: Oskar Thorén <oskar@status.im>, Sanaz Taheri <sanaz@status.im>
---
# Table of Contents
@ -12,9 +12,10 @@ authors: Oskar Thorén <oskar@status.im>
- [WakuMessage](#wakumessage)
- [Protobuf](#protobuf)
- [Payload encryption](#payload-encryption)
- [Version 0](#version-0)
- [Version 1](#version-1)
- [Version 0](#version-0)
- [Version 1 (not yet implemented in Waku v2)](#version-1-not-yet-implemented-in-waku-v2)
- [Differences from Whisper / Waku v1 envelopes](#differences-from-whisper--waku-v1-envelopes)
- [Security Consideration](#security-consideration)
- [Changelog](#changelog)
- [Copyright](#copyright)
@ -76,6 +77,10 @@ topic, data, nonce`.
Since Waku v2 is using libp2p PubSub, some of these fields can be dropped. The previous `topic`
field corresponds to `contentTopic`. The previous `data` field corresponds to the `payload` field.
# Security Consideration
In Waku, the confidentiality, integrity, and authenticity of the data must be addressed at the `WakuMessage` level. That is, the `payload` shall be encrypted or signed properly to meet the application-specific privacy needs.
# Changelog
Initial release on [2020-10-22](https://github.com/vacp2p/specs/pull/222/commits/dbab6c7084b414b62818150588266abedd09315f).