mirror of
https://github.com/meshcore-dev/MeshCore.git
synced 2026-08-14 05:09:46 +00:00
deploy: 03b6ef4b0d
This commit is contained in:
@@ -2206,6 +2206,8 @@ Bytes 9 .. 8+data_len: Payload
|
||||
<li>Uses a secret key derived from the channel name</li>
|
||||
<li>It is the first 16 bytes of <code>sha256("#test")</code></li>
|
||||
<li>For example hashtag channel <code>#test</code> has the key: <code>9cd8fcf22a47333b591d96a2b848b73f</code></li>
|
||||
<li>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.</li>
|
||||
<li>Used as a topic based public group chat, separate from the default public channel</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -1278,6 +1278,8 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<p>The plaintext contained in the ciphertext matches the format described in <a href="#plain-text-message">plain text message</a>. Specifically, it consists of a four byte timestamp, a flags byte, and the message. The flags byte will generally be <code>0x00</code> because it is a "plain text message". The message will be of the form <code><sender name>: <message body></code> (eg., <code>user123: I'm on my way</code>).</p>
|
||||
<p>The sender name is unverified message text. Group messages contain no sender
|
||||
signature, so any channel-key holder can choose any sender name.</p>
|
||||
<h1 id="group-datagram">Group datagram</h1>
|
||||
<table>
|
||||
<thead>
|
||||
|
||||
File diff suppressed because one or more lines are too long
+13
-13
@@ -2,54 +2,54 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/cli_commands/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/companion_protocol/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/docs/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/faq/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/kiss_modem_protocol/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/nrf52_power_management/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/number_allocations/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/packet_format/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/payloads/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/qr_codes/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/stats_binary_frames/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/terminal_chat_cli/</loc>
|
||||
<lastmod>2026-07-19</lastmod>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user