From 7676ae9184b3f08d2be73a869963cf42c27317da Mon Sep 17 00:00:00 2001 From: geeksville Date: Fri, 19 Jun 2020 13:57:10 -0700 Subject: [PATCH 1/3] 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 fe6ab93b3a..cd9f288898 100644 --- a/docs/software/crypto.md +++ b/docs/software/crypto.md @@ -14,13 +14,13 @@ Based on comments from reviewers (see below), here's some tips for usage of thes * 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 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 tommorw or in the past - if they kept a raw copy of those broadcast packets) +* 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): 1. Optionally requiring users to provide a PIN to regain access to the mesh. This could be based on: intentionally locking the device, time since last use, or any member could force all members to reauthenticate, 2. Until a device reauthenticates, any other access via BLE or USB would be blocked (this would protect against attackers who are not prepared to write custom software to extract and reverse engineer meshtastic flash memory) -3. Turning on read-back protection in the device fuse-bits (this would extend protection in #2 to block all but **extensively** advanced attacks involving chip disassembly) +3. Turning on read-back protection in the device fuse-bits (this would extend protection in #2 to block all but **extremely** advanced attacks involving chip disassembly) 4. Time limiting keys used for message transmission and automatically cycling them on a schedule. This would protect past messages from being decoded even if an attacker learns the current key. ### Notes for reviewers From 60b38215cea66ec027473d2b4a9088bf1fe25b25 Mon Sep 17 00:00:00 2001 From: geeksville Date: Sat, 20 Jun 2020 09:58:45 -0700 Subject: [PATCH 2/3] fix docs per @feh123 --- docs/software/build-instructions.md | 2 +- platformio.ini | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/software/build-instructions.md b/docs/software/build-instructions.md index 5074fbaf1f..d3a63712a5 100644 --- a/docs/software/build-instructions.md +++ b/docs/software/build-instructions.md @@ -7,7 +7,7 @@ in these instructions I describe use of their command line tool. 2. Install [PlatformIO](https://platformio.org/platformio-ide) 3. Download this git repo and cd into it 4. Run `git submodule update --init --recursive` to pull in dependencies this project needs. -5. If you are outside the USA, edit [platformio.ini](/platformio.ini) to set the correct frequency range for your country. The line you need to change starts with `hw_version` and instructions are provided above that line. Options are provided for `EU433`, `EU835`, `CN`, `JP` and `US` (default). Pull-requests eagerly accepted for other countries. +5. If you are outside the USA, run "export COUNTRY=EU865" (or whatever) to set the correct frequency range for your country. Options are provided for `EU433`, `EU865`, `CN`, `JP` and `US` (default). Pull-requests eagerly accepted for other countries. 6. Plug the radio into your USB port 7. Type `pio run --environment XXX -t upload` (This command will fetch dependencies, build the project and install it on the board via USB). For XXX, use the board type you have (either `tbeam`, `heltec`, `ttgo-lora32-v1`, `ttgo-lora32-v2`). 8. Platform IO also installs a very nice VisualStudio Code based IDE, see their [tutorial](https://docs.platformio.org/en/latest/tutorials/espressif32/arduino_debugging_unit_testing.html) if you'd like to use it. diff --git a/platformio.ini b/platformio.ini index 4ac4fa25f8..298032cec3 100644 --- a/platformio.ini +++ b/platformio.ini @@ -17,7 +17,7 @@ default_envs = tbeam ; Note: the github actions CI test build can't yet build NR ; REQUIRED environment variables - if not set the specified default will be sued ; The following environment variables must be set in the shell if you'd like to override them. ; They are used in this ini file as systenv.VARNAME, so in your shell do export "VARNAME=fish" -; HW_VERSION (default US) +; COUNTRY (default US), i.e. "export COUNTRY=EU865" ; APP_VERSION (default emptystring) ; HW_VERSION (default emptystring) From b11b322581724c6724adeb35ced58f5c163427b0 Mon Sep 17 00:00:00 2001 From: geeksville Date: Sat, 20 Jun 2020 14:53:25 -0700 Subject: [PATCH 3/3] 0.7.8 --- bin/version.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/version.sh b/bin/version.sh index c9bcc7743c..7cc716c143 100644 --- a/bin/version.sh +++ b/bin/version.sh @@ -1,3 +1,3 @@ -export VERSION=0.7.7 \ No newline at end of file +export VERSION=0.7.8 \ No newline at end of file