mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-11-09 23:24:10 -08:00
Add meta descriptions for all of the pages under About
This commit is contained in:
parent
e36391d4a7
commit
b44ec621bc
|
@ -3,6 +3,7 @@ title: Contributing to Meshtastic
|
|||
sidebar_label: Contributing
|
||||
slug: /contributing
|
||||
sidebar_position: 3
|
||||
description: "Get involved with Meshtastic's open-source project. Contribute to device firmware, web apps, or mobile and desktop apps. Your expertise can help enhance this volunteer-driven communication platform."
|
||||
---
|
||||
|
||||
import Link from "@docusaurus/Link"
|
||||
|
|
|
@ -3,6 +3,7 @@ id: faq
|
|||
title: FAQs
|
||||
slug: /faq
|
||||
sidebar_position: 3
|
||||
description: "Find answers to your Meshtastic questions: from getting started, device setup, to advanced features. Learn about app compatibility, channel sharing, and HAM license benefits. Dive into our comprehensive FAQ."
|
||||
---
|
||||
|
||||
import { FaqAccordion } from "/src/components/FaqAccordion";
|
||||
|
|
|
@ -3,6 +3,7 @@ title: Introduction
|
|||
sidebar_label: Introduction
|
||||
slug: /introduction
|
||||
sidebar_position: 1
|
||||
description: "Discover Meshtastic: a community-driven, open-source project using LoRa radios for long-range, off-grid communication."
|
||||
---
|
||||
|
||||
import Link from "@docusaurus/Link";
|
||||
|
|
|
@ -4,6 +4,7 @@ title: Meshtastic Encryption
|
|||
sidebar_label: Encryption
|
||||
slug: /overview/encryption
|
||||
sidebar_position: 3
|
||||
description: "Understand Meshtastic's encryption: optional network-wide AES256 security for off-grid communication, ensuring confidentiality against passive eavesdropping."
|
||||
---
|
||||
|
||||
|
||||
|
@ -57,4 +58,4 @@ I'm assuming that meshtastic is being used to hike in places where someone capab
|
|||
- I think the bigger encryption question is "what does the encryption need to do"? As it stands, an attacker who has yet to capture any of the devices cannot reasonably capture text or location data. An attacker who captures any device in the channel/mesh can read everything going to that device, everything stored on that device, and any other communication within the channel that they captured in encrypted form. If that capability basically matches your expectations, it is suitable for whatever adventures this was intended for, then, based on information publicly available or widely disclosed, the encryption is good. If those properties are distressing (like, device history is deliberately limited and you don't want a device captured today to endanger the information sent over the channel yesterday) we could talk about ways to achieve that (most likely synchronizing time and replacing the key with its own SHA256 every X hours, and ensuring the old key is not retained unnecessarily).
|
||||
- Two other things to keep in mind are that AES-CTR does not itself provide authenticity (e.g. an attacker can flip bits in replaying data and scramble the resulting plaintext), and that the current scheme gives some hints about transmission in the size. So, if you worry about an adversary deliberately messing-up messages or knowing the length of a text message, it looks like those might be possible.
|
||||
|
||||
I'm guessing that the network behaves somewhat like a store-and-forward network - or, at least, that the goal is to avoid establishing a two-way connection to transmit data. I'm afraid I haven't worked with mesh networks much, but remember studying them briefly in school about ten years ago.
|
||||
I'm guessing that the network behaves somewhat like a store-and-forward network - or, at least, that the goal is to avoid establishing a two-way connection to transmit data. I'm afraid I haven't worked with mesh networks much, but remember studying them briefly in school about ten years ago.
|
||||
|
|
|
@ -3,6 +3,7 @@ title: Overview
|
|||
sidebar_label: Overview
|
||||
slug: /overview
|
||||
sidebar_position: 2
|
||||
description: "Discover the basics of Meshtastic's operation, from sending messages via the companion app to the network's intelligent rebroadcast system for extended reach."
|
||||
---
|
||||
|
||||
## How it works
|
||||
|
|
|
@ -4,6 +4,7 @@ title: Mesh Broadcast Algorithm
|
|||
slug: /overview/mesh-algo
|
||||
sidebar_label: Mesh Algorithm
|
||||
sidebar_position: 2
|
||||
description: "Discover the Meshtastic Mesh Broadcast Algorithm: a simple, yet effective routing protocol designed for off-grid communication using LoRa technology."
|
||||
---
|
||||
|
||||
## Current Algorithm
|
||||
|
|
|
@ -4,6 +4,7 @@ title: Radio Settings
|
|||
slug: /overview/radio-settings
|
||||
sidebar_label: Radio Settings
|
||||
sidebar_position: 1
|
||||
description: "Maximize your Meshtastic device's potential with detailed radio settings instructions, including frequency bands, data rates, and encryption options."
|
||||
---
|
||||
|
||||
import {FrequencyCalculator} from "/src/components/tools/FrequencyCalculator";
|
||||
|
|
|
@ -4,6 +4,7 @@ title: Range Tests
|
|||
slug: /overview/range-tests
|
||||
sidebar_label: Range Tests
|
||||
sidebar_position: 4
|
||||
description: "Explore Meshtastic's impressive range achievements with detailed modem settings and device configurations for both ground and air records."
|
||||
---
|
||||
|
||||
import Tabs from "@theme/Tabs";
|
||||
|
|
Loading…
Reference in a new issue