From 6f6dd2291efecaf9e90a2fdcae3686793254f8a7 Mon Sep 17 00:00:00 2001 From: Kevin Hester Date: Thu, 28 Jan 2021 10:30:00 +0800 Subject: [PATCH] fix typo --- docs/software/crypto.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/software/crypto.md b/docs/software/crypto.md index cd9f2888..1ee7c6d5 100644 --- a/docs/software/crypto.md +++ b/docs/software/crypto.md @@ -13,7 +13,7 @@ the project developers are not cryptography experts. Therefore we ask two things Based on comments from reviewers (see below), here's some tips for usage of these radios. So you can know the level of protection offered: * It is pretty likely that the AES256 security is implemented 'correctly' and an observer will not be able to decode your messages. -* Warning: If an attacker is able to get one of the radios in their position, they could either a) extract the channel key from that device or b) use that radio to listen to new communications. +* Warning: If an attacker is able to get one of the radios in their posession, they could either a) extract the channel key from that device or b) use that radio to listen to new communications. * Warning: If an attacker is able to get the "Channel QR code/URL" that you share with others - that attacker could then be able to read any messages sent on the channel (either tomorrow or in the past - if they kept a raw copy of those broadcast packets) Possible future areas of work (if there is enough interest - post in our [forum](https://meshtastic.discourse.group) if you want this): @@ -48,4 +48,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. \ No newline at end of file +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.