mirror of
https://github.com/meshcore-dev/MeshCore.git
synced 2026-08-14 11:39:48 +00:00
Clarify hashtag privacy and group sender identity
This commit is contained in:
@@ -440,6 +440,8 @@ Byte 0: 0x14
|
||||
- Uses a secret key derived from the channel name
|
||||
- It is the first 16 bytes of `sha256("#test")`
|
||||
- For example hashtag channel `#test` has the key: `9cd8fcf22a47333b591d96a2b848b73f`
|
||||
- Traffic is encrypted on air, but anyone who knows or guesses the channel
|
||||
name can derive the key. Hashtag channels should not be treated as private.
|
||||
- Used as a topic based public group chat, separate from the default public channel
|
||||
3. **Private Channels**
|
||||
- Uses a randomly generated 16-byte secret key
|
||||
|
||||
@@ -236,6 +236,9 @@ txt_type
|
||||
|
||||
The plaintext contained in the ciphertext matches the format described in [plain text message](#plain-text-message). Specifically, it consists of a four byte timestamp, a flags byte, and the message. The flags byte will generally be `0x00` because it is a "plain text message". The message will be of the form `<sender name>: <message body>` (eg., `user123: I'm on my way`).
|
||||
|
||||
The sender name is unverified message text. Group messages contain no sender
|
||||
signature, so any channel-key holder can choose any sender name.
|
||||
|
||||
# Group datagram
|
||||
|
||||
| Field | Size (bytes) | Description |
|
||||
|
||||
Reference in New Issue
Block a user