From 3ea0bc9f530a0ccfe49127c73ca53992b0e09fa5 Mon Sep 17 00:00:00 2001 From: James Rich <2199651+jamesarich@users.noreply.github.com> Date: Sat, 5 Sep 2026 17:09:54 -0700 Subject: [PATCH] chore: Scheduled updates (Firmware, Hardware, Translations) (#7052) --- .../composeResources/values-ar/strings.xml | 1 - .../composeResources/values-bg/strings.xml | 2 -- .../composeResources/values-cs/strings.xml | 2 -- .../composeResources/values-de/strings.xml | 2 -- .../composeResources/values-el/strings.xml | 1 - .../composeResources/values-es/strings.xml | 1 - .../composeResources/values-et/strings.xml | 2 -- .../composeResources/values-fi/strings.xml | 2 -- .../composeResources/values-fr/strings.xml | 2 -- .../composeResources/values-ga/strings.xml | 1 - .../composeResources/values-ht/strings.xml | 1 - .../composeResources/values-hu/strings.xml | 2 -- .../composeResources/values-it/strings.xml | 2 -- .../composeResources/values-ja/strings.xml | 2 -- .../composeResources/values-ko/strings.xml | 1 - .../composeResources/values-lt/strings.xml | 1 - .../composeResources/values-nl/strings.xml | 1 - .../composeResources/values-no/strings.xml | 1 - .../composeResources/values-pl/strings.xml | 2 -- .../composeResources/values-pt-rBR/strings.xml | 1 - .../composeResources/values-pt/strings.xml | 1 - .../composeResources/values-ro/strings.xml | 2 -- .../composeResources/values-ru/strings.xml | 2 -- .../composeResources/values-sk/strings.xml | 1 - .../composeResources/values-sl/strings.xml | 1 - .../composeResources/values-sq/strings.xml | 1 - .../composeResources/values-sr/strings.xml | 1 - .../composeResources/values-srp/strings.xml | 1 - .../composeResources/values-sv/strings.xml | 2 -- .../composeResources/values-tr/strings.xml | 1 - .../composeResources/values-uk/strings.xml | 2 -- .../composeResources/values-zh-rCN/strings.xml | 2 -- .../composeResources/values-zh-rTW/strings.xml | 2 -- docs/ar-rSA/user/nodes.md | 12 ++++++------ docs/be-rBY/user/nodes.md | 12 ++++++------ docs/bg-rBG/user/nodes.md | 12 ++++++------ docs/ca-rES/user/nodes.md | 12 ++++++------ docs/cs-rCZ/user/nodes.md | 12 ++++++------ docs/de-rDE/user/nodes.md | 12 ++++++------ docs/el-rGR/user/nodes.md | 12 ++++++------ docs/es-rES/user/nodes.md | 12 ++++++------ docs/et-rEE/user/nodes.md | 12 ++++++------ docs/fi-rFI/user/nodes.md | 4 ++-- docs/fr-rCA/user/nodes.md | 12 ++++++------ docs/fr-rFR/user/nodes.md | 12 ++++++------ docs/ga-rIE/user/nodes.md | 12 ++++++------ docs/gl-rES/user/nodes.md | 12 ++++++------ docs/hr-rHR/user/nodes.md | 12 ++++++------ docs/ht-rHT/user/nodes.md | 12 ++++++------ docs/hu-rHU/user/nodes.md | 12 ++++++------ docs/is-rIS/user/nodes.md | 12 ++++++------ docs/it-rIT/user/nodes.md | 12 ++++++------ docs/iw-rIL/user/nodes.md | 12 ++++++------ docs/ja-rJP/user/nodes.md | 12 ++++++------ docs/ko-rKR/user/nodes.md | 12 ++++++------ docs/lt-rLT/user/nodes.md | 12 ++++++------ docs/nl-rNL/user/nodes.md | 12 ++++++------ docs/no-rNO/user/nodes.md | 12 ++++++------ docs/pl-rPL/user/nodes.md | 12 ++++++------ docs/pt-rBR/user/nodes.md | 12 ++++++------ docs/pt-rPT/user/nodes.md | 12 ++++++------ docs/ro-rRO/user/nodes.md | 12 ++++++------ docs/ru-rRU/user/nodes.md | 12 ++++++------ docs/sk-rSK/user/nodes.md | 12 ++++++------ docs/sl-rSI/user/nodes.md | 12 ++++++------ docs/sq-rAL/user/nodes.md | 12 ++++++------ docs/sr-rLatn/user/nodes.md | 12 ++++++------ docs/srp/user/nodes.md | 12 ++++++------ docs/sv-rSE/user/nodes.md | 12 ++++++------ docs/tr-rTR/user/nodes.md | 12 ++++++------ docs/uk-rUA/user/nodes.md | 12 ++++++------ docs/zh-rCN/user/nodes.md | 12 ++++++------ docs/zh-rTW/user/nodes.md | 12 ++++++------ 73 files changed, 236 insertions(+), 285 deletions(-) diff --git a/core/resources/src/commonMain/composeResources/values-ar/strings.xml b/core/resources/src/commonMain/composeResources/values-ar/strings.xml index 397440a591..1a899307cd 100644 --- a/core/resources/src/commonMain/composeResources/values-ar/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ar/strings.xml @@ -90,7 +90,6 @@ المفتاح العام غير متطابق تشفير المفتاح العام - مفتاح مشترك غلط diff --git a/core/resources/src/commonMain/composeResources/values-bg/strings.xml b/core/resources/src/commonMain/composeResources/values-bg/strings.xml index a2697f03f7..45ce73166e 100644 --- a/core/resources/src/commonMain/composeResources/values-bg/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-bg/strings.xml @@ -413,8 +413,6 @@ Публичният ключ не съвпада със записания ключ. Можете да премахнете възела и да го оставите да обмени ключове отново, но това може да показва по-сериозен проблем със сигурността. Свържете се с потребителя чрез друг надежден канал, за да определите дали промяната на ключа се дължи на фабрично нулиране или друго умишлено действие. Криптиране с публичния ключ Директните съобщения използват новата инфраструктура с публичен ключ за криптиране. - Споделен ключ - Могат да се изпращат/получават само съобщения в каналите. Директните съобщения изискват функцията Инфраструктура с публичен ключ във фърмуер 2.5+. Показатели на околната среда Околна среда diff --git a/core/resources/src/commonMain/composeResources/values-cs/strings.xml b/core/resources/src/commonMain/composeResources/values-cs/strings.xml index 61d04ccc6d..9c3176f503 100644 --- a/core/resources/src/commonMain/composeResources/values-cs/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-cs/strings.xml @@ -545,8 +545,6 @@ Veřejný klíč neodpovídá uloženému klíči. Můžete uzel odebrat a nechat jej znovu vyměnit klíče, ale může to znamenat bezpečnostní problém. Kontaktujte uživatele jiným důvěryhodným kanálem a ověřte, zda ke změně klíče došlo v důsledku továrního resetu nebo jiné úmyslné akce. Šifrování veřejného klíče Přímé zprávy používají novou infrastrukturu veřejných klíčů pro šifrování. - Sdílený klíč - Lze odesílat a přijímat pouze kanálové zprávy. Přímé zprávy vyžadují funkci infrastruktury veřejných klíčů (PKI) ve firmwaru verze 2.5 a vyšší. Metriky prostředí Životní prostředí diff --git a/core/resources/src/commonMain/composeResources/values-de/strings.xml b/core/resources/src/commonMain/composeResources/values-de/strings.xml index 99e4b93168..414a7cbad8 100644 --- a/core/resources/src/commonMain/composeResources/values-de/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-de/strings.xml @@ -535,8 +535,6 @@ Der öffentliche Schlüssel stimmt nicht mit dem gespeicherten Schlüssel überein. Sie können den Knoten entfernen und den Schlüsselaustausch erneut durchführen lassen. Dies könnte jedoch auf ein schwerwiegenderes Sicherheitsproblem hindeuten. Kontaktieren Sie den Benutzer über einen anderen vertrauenswürdigen Kanal, um zu klären, ob die Schlüsseländerung auf ein Zurücksetzen auf Werkseinstellungen oder eine andere absichtliche Handlung zurückzuführen ist. Verschlüsselung mit öffentlichen Schlüssel Direktnachrichten verwenden zur den öffentlichen Knotenschlüssel zur Verschlüsselung. - Geteilter Schlüssel - Es können nur Kanalnachrichten gesendet/empfangen werden. Direktnachrichten erfordern die Verschlüsselung mit öffentlichem Knotenschlüssel seit Firmware 2.5+. Umweltdaten Umgebung diff --git a/core/resources/src/commonMain/composeResources/values-el/strings.xml b/core/resources/src/commonMain/composeResources/values-el/strings.xml index 16d53dd953..abb1c225b0 100644 --- a/core/resources/src/commonMain/composeResources/values-el/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-el/strings.xml @@ -100,7 +100,6 @@ Ασυμφωνία δημόσιου κλειδιού Κρυπτογράφηση Δημόσιου Κλειδιού - Κοινόχρηστο Κλειδί Σφάλμα diff --git a/core/resources/src/commonMain/composeResources/values-es/strings.xml b/core/resources/src/commonMain/composeResources/values-es/strings.xml index 4cdef8cdf7..7fae0d2d9e 100644 --- a/core/resources/src/commonMain/composeResources/values-es/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-es/strings.xml @@ -286,7 +286,6 @@ Clave pública no coincide Cifrado de Clave Pública Los mensajes directos están utilizando la nueva infraestructura de clave pública para el cifrado. - Clave compartida Métricas de Entorno Ambiente diff --git a/core/resources/src/commonMain/composeResources/values-et/strings.xml b/core/resources/src/commonMain/composeResources/values-et/strings.xml index b663e3bbd1..f65e5fd555 100644 --- a/core/resources/src/commonMain/composeResources/values-et/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-et/strings.xml @@ -608,8 +608,6 @@ Avalikvõti ei ühti salvestatud võtmele. Võid sõlme eemaldada ja lasta uuesti võtmeid vahetada, kuid see võib viidata tõsisemale turvaprobleemile. Võtke kasutajaga ühendust mõne muu usaldusväärse kanali kaudu, et teha kindlaks, kas võtmevahetus oli tingitud tehaseseadete taastamisest või muust tahtlikust toimingust. Avaliku võtme krüpteerimine Otsesõnumid kasutavad krüpteerimiseks uut avaliku võtme infrastruktuuri. - Jagatud võti - Saata/vastuvõtta saab ainult kanali-sõnumeid. Otsesõnumid nõuavad avaliku võtme infrastruktuuri funktsiooni püsivara versioonist 2.5 alates. Keskkonnamõõdikud Keskkond diff --git a/core/resources/src/commonMain/composeResources/values-fi/strings.xml b/core/resources/src/commonMain/composeResources/values-fi/strings.xml index 8a9bc122d7..66071d3b80 100644 --- a/core/resources/src/commonMain/composeResources/values-fi/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-fi/strings.xml @@ -621,8 +621,6 @@ Julkinen avain ei vastaa tallennettua avainta. Voit poistaa laitteen ja antaa sen vaihtaa avaimet uudelleen, mutta tämä saattaa viitata vakavampaan tietoturvaongelmaan. Ota yhteyttä käyttäjään toista luotettua kanavaa pitkin selvittääksesi, johtuuko avaimen vaihtuminen tehdasasetusten palautuksesta tai muusta tarkoituksellisesta toimenpiteestä. Julkisen avaimen salaus Yksityisviesteissä käytetään uutta julkisen avaimen infrastruktuuria salaukseen. - Jaettu avain - Voit lähettää ja vastaanottaa vain kanavaviestejä. Yksityisviestit toimivat vasta, kun käytössä on ohjelmistoversio 2.5+ tai uudempi, jossa on tuki salausavaimille. Ympäristöarvot Ympäristö diff --git a/core/resources/src/commonMain/composeResources/values-fr/strings.xml b/core/resources/src/commonMain/composeResources/values-fr/strings.xml index 88bb7644db..1ee0e7f9d7 100644 --- a/core/resources/src/commonMain/composeResources/values-fr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-fr/strings.xml @@ -549,8 +549,6 @@ La clé publique ne correspond pas à la clé enregistrée. Vous pouvez supprimer le nœud et le laisser à nouveau échanger les clés, mais cela peut indiquer un problème de sécurité plus grave. Contactez l'utilisateur à travers un autre canal de confiance, pour déterminer si le changement de clé est dû à une réinitialisation d'usine ou à une autre action intentionnelle. Chiffrement de clé publique Les messages directs utilisent la nouvelle infrastructure de clé publique pour le chiffrement. - Clé partagée - Seuls les messages vers les canaux peuvent être senvoyés/reçus. Les messages directs nécessitent la fonctionnalité d'infrastructure de clé publique disponible dans le firmware 2.5+. Métriques d'environnement Environnement diff --git a/core/resources/src/commonMain/composeResources/values-ga/strings.xml b/core/resources/src/commonMain/composeResources/values-ga/strings.xml index 0f68ca41fe..10f40935c5 100644 --- a/core/resources/src/commonMain/composeResources/values-ga/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ga/strings.xml @@ -90,7 +90,6 @@ Mícomhoiriúnacht na heochrach phoiblí Cóid Poiblí Eochair - Eochair roinnte Earráid Teorainn na Ciorcad Oibre bainte. Ní féidir teachtaireachtaí a sheoladh faoi láthair, déan iarracht arís níos déanaí. diff --git a/core/resources/src/commonMain/composeResources/values-ht/strings.xml b/core/resources/src/commonMain/composeResources/values-ht/strings.xml index 4e96c37bbb..e16e2e027c 100644 --- a/core/resources/src/commonMain/composeResources/values-ht/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ht/strings.xml @@ -87,7 +87,6 @@ Pa matche kle piblik Chifreman Kle Piblik - Kle Pataje Erè Limit sik devwa rive. Pa ka voye mesaj kounye a, tanpri eseye ankò pita. diff --git a/core/resources/src/commonMain/composeResources/values-hu/strings.xml b/core/resources/src/commonMain/composeResources/values-hu/strings.xml index fa96c523e6..f29881f8d2 100644 --- a/core/resources/src/commonMain/composeResources/values-hu/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-hu/strings.xml @@ -290,8 +290,6 @@ Publikus kulcs nem egyezik Publikus Kulcs Titkosítás A közvetlen üzenetek az új nyilvános kulcsú infrastruktúrát használják titkosításhoz. - Megosztott kulcs - Csak csatornaüzenetek küldhetők/fogadhatók. Közvetlen üzenetekhez a 2.5+ firmware PKI funkciója szükséges. Környezeti metrikák Környezet diff --git a/core/resources/src/commonMain/composeResources/values-it/strings.xml b/core/resources/src/commonMain/composeResources/values-it/strings.xml index aebece1f27..3e9b02c451 100644 --- a/core/resources/src/commonMain/composeResources/values-it/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-it/strings.xml @@ -571,8 +571,6 @@ La chiave pubblica non corrisponde alla chiave salvata. È possibile rimuovere il nodo e lasciarlo scambiare le chiavi nuovamente, ma questo può indicare un problema di sicurezza più serio. Contattare l'utente attraverso un altro canale attendibile, per determinare se il cambiamento di chiave è dovuto a un ripristino di fabbrica o ad altre azioni intenzionali. Crittografia a Chiave Pubblica I messaggi diretti stanno usando la crittografia basata sulla nuova infrastruttura a chiave pubblica. - Chiave Condivisa - Solo i messaggi del canale possono essere inviati/ricevuti. I messaggi diretti necessitano dell'Infrastruttura a Chiave Pubblica, presente nel firmware 2.5+. Metriche Ambientali Ambiente diff --git a/core/resources/src/commonMain/composeResources/values-ja/strings.xml b/core/resources/src/commonMain/composeResources/values-ja/strings.xml index ce7ccd0580..0912355c4c 100644 --- a/core/resources/src/commonMain/composeResources/values-ja/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ja/strings.xml @@ -565,8 +565,6 @@ 公開鍵が記録されている鍵と一致しません。ノードを削除して鍵を再交換させることもできますが、これはより深刻なセキュリティ上の問題を示している可能性があります。鍵の変更が工場出荷時リセットやその他の意図的な操作によるものかどうかを確認するため、別の信頼できる手段でユーザーに連絡してください。 公開鍵暗号化 ダイレクトメッセージは、暗号化に新しい公開鍵基盤を使用しています。 - 共有鍵 - チャンネルメッセージのみ送受信できます。ダイレクトメッセージには、2.5 以降のファームウェアの公開鍵基盤機能が必要です。 環境メトリクス 環境 diff --git a/core/resources/src/commonMain/composeResources/values-ko/strings.xml b/core/resources/src/commonMain/composeResources/values-ko/strings.xml index 8d4ee2a21d..859c47d261 100644 --- a/core/resources/src/commonMain/composeResources/values-ko/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ko/strings.xml @@ -179,7 +179,6 @@ 암호화 사용 공개 키가 일치하지 않습니다 공개 키 암호화 - 공유 키 환경 환경 메트릭 모듈 사용 diff --git a/core/resources/src/commonMain/composeResources/values-lt/strings.xml b/core/resources/src/commonMain/composeResources/values-lt/strings.xml index 8113307b0c..66ffcae8d9 100644 --- a/core/resources/src/commonMain/composeResources/values-lt/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-lt/strings.xml @@ -91,7 +91,6 @@ Viešojo rakto neatitikimas Viešojo rakto šifruotė - Viešas raktas Klaida Pasiektas veikimo ciklo limitas. Šiuo metu negalima siųsti žinučių, bandykite vėliau. diff --git a/core/resources/src/commonMain/composeResources/values-nl/strings.xml b/core/resources/src/commonMain/composeResources/values-nl/strings.xml index 17d33ca47d..1b1a73082c 100644 --- a/core/resources/src/commonMain/composeResources/values-nl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-nl/strings.xml @@ -145,7 +145,6 @@ Encryptie ingeschakeld Publieke sleutel komt niet overeen Publieke sleutel encryptie - Gedeelde Key Omgeving Fout diff --git a/core/resources/src/commonMain/composeResources/values-no/strings.xml b/core/resources/src/commonMain/composeResources/values-no/strings.xml index edbbf25850..8906c74d61 100644 --- a/core/resources/src/commonMain/composeResources/values-no/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-no/strings.xml @@ -92,7 +92,6 @@ Direktemeldinger bruker den nye offentlige nøkkelinfrastrukturen for kryptering. Krever firmware versjon 2.5 eller høyere. Offentlig-nøkkel kryptering - Delt nøkkel Feil Grensen for sykluser er nådd. Kan ikke sende meldinger akkurat nå, prøv igjen senere. diff --git a/core/resources/src/commonMain/composeResources/values-pl/strings.xml b/core/resources/src/commonMain/composeResources/values-pl/strings.xml index 6be43f915e..77a138b572 100644 --- a/core/resources/src/commonMain/composeResources/values-pl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pl/strings.xml @@ -265,8 +265,6 @@ Klucz publiczny nie pasuje do zapisanego klucza. Możesz usunąć węzeł i pozwolić mu na ponowną wymianę kluczy, ale może to oznaczać poważniejszy problem z bezpieczeństwem. Skontaktuj się z użytkownikiem przez inny zaufany kanał, żeby sprawdzić, czy zmiana klucza była spowodowana przywróceniem ustawień fabrycznych lub innym celowym działaniem. Szyfrowanie klucza publicznego Bezpośrednie wiadomości wykorzystują nową infrastrukturę klucza publicznego do szyfrowania. - Klucz współdzielony - Tylko wiadomości kanału mogą być wysyłane/odbierane. Bezpośrednie wiadomości wymagają funkcji infrastruktury klucza publicznego w oprogramowaniu 2.5+. Metryki środowiskowe Środowisko diff --git a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml index 71bb8fb1b7..3c22aac952 100644 --- a/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml @@ -255,7 +255,6 @@ Criptografia ativada Chave pública não confere Criptografia de Chave Pública - Chave Compartilhada Ambiente Módulo de métricas do ambiente ativado diff --git a/core/resources/src/commonMain/composeResources/values-pt/strings.xml b/core/resources/src/commonMain/composeResources/values-pt/strings.xml index 4e82cfef47..cd9c126b01 100644 --- a/core/resources/src/commonMain/composeResources/values-pt/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-pt/strings.xml @@ -177,7 +177,6 @@ Encriptação ativada Incompatibilidade de chave pública Criptografia de chave pública - Chave partilhada Ambiente Módulo de métricas de ambiente ativado diff --git a/core/resources/src/commonMain/composeResources/values-ro/strings.xml b/core/resources/src/commonMain/composeResources/values-ro/strings.xml index 8c730d7540..27bd9951e8 100644 --- a/core/resources/src/commonMain/composeResources/values-ro/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ro/strings.xml @@ -339,8 +339,6 @@ Cheia publică nu corespunde cu cheia înregistrată. Puteți elimina nodul și permiteți schimbul de chei din nou, dar acest lucru poate indica o problemă de securitate mai gravă. Contactați utilizatorul printr-un alt canal de încredere, pentru a determina dacă schimbarea cheii s-a datorat unei resetări la setările din fabrică sau unei alte acțiuni intenționate. Criptare cu cheie publică Mesajele directe utilizează noua infrastructură cu cheie publică pentru criptare. - Cheie partajată - Se pot trimite/primi numai mesaje de canal. Mesajele directe necesită infrastructura cu chei publice din firmware-ul 2.5+. Indicatori de mediu Mediu diff --git a/core/resources/src/commonMain/composeResources/values-ru/strings.xml b/core/resources/src/commonMain/composeResources/values-ru/strings.xml index 5dcbb30575..afc4c7e6c9 100644 --- a/core/resources/src/commonMain/composeResources/values-ru/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-ru/strings.xml @@ -617,8 +617,6 @@ Открытый ключ не соответствует записанному ключу. Вы можете удалить ноду и позволить ей снова обменяться ключами, но это может указывать на серьезную проблему с безопасностью. Свяжитесь с пользователем по другому надежному каналу чтобы определить, произошла ли смена ключа в результате сброса настроек или другого преднамеренного действия. Общий ключ шифрования Прямые сообщения используют новую инфраструктуру открытого ключа для шифрования. - Общедоступный ключ - Только сообщения каналов могут быть отправлены/получены. Прямые сообщения требуют поддержки Инфраструктуры Открытого Ключа (PKI) в 2.5+ прошивке. Метрики окружения Окружающая среда diff --git a/core/resources/src/commonMain/composeResources/values-sk/strings.xml b/core/resources/src/commonMain/composeResources/values-sk/strings.xml index e4dcbb4b7c..a0435e3fb7 100644 --- a/core/resources/src/commonMain/composeResources/values-sk/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sk/strings.xml @@ -152,7 +152,6 @@ Nezhoda verejného kľúča Šifrovanie verejného kľúča - Zdieľaný kľúč Prostredie Chyba diff --git a/core/resources/src/commonMain/composeResources/values-sl/strings.xml b/core/resources/src/commonMain/composeResources/values-sl/strings.xml index 2ba204a4c0..46147d20bd 100644 --- a/core/resources/src/commonMain/composeResources/values-sl/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sl/strings.xml @@ -94,7 +94,6 @@ Neujemanje javnega ključa Šifriranje javnega ključa - Skupni ključ Napaka Dosežena je omejitev delovnega cikla. Trenutno ne morete pošiljati sporočil, poskusite kasneje. diff --git a/core/resources/src/commonMain/composeResources/values-sq/strings.xml b/core/resources/src/commonMain/composeResources/values-sq/strings.xml index 471ec9e4c4..0b58734790 100644 --- a/core/resources/src/commonMain/composeResources/values-sq/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sq/strings.xml @@ -92,7 +92,6 @@ Përputhje e Gabuar e Çelësit Publik Kriptimi me Çelës Publik - Çelësi i Përbashkët Gabim Cikli i detyrës ka arritur kufirin. Nuk mund të dërgoni mesazhe tani, ju lutem provoni përsëri më vonë. diff --git a/core/resources/src/commonMain/composeResources/values-sr/strings.xml b/core/resources/src/commonMain/composeResources/values-sr/strings.xml index 26d789c477..3903837c6d 100644 --- a/core/resources/src/commonMain/composeResources/values-sr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sr/strings.xml @@ -176,7 +176,6 @@ Неусаглашеност јавних кључева Шифровање јавним кључем - Дељени кључ Метрике сензора Окружење diff --git a/core/resources/src/commonMain/composeResources/values-srp/strings.xml b/core/resources/src/commonMain/composeResources/values-srp/strings.xml index e25e84736c..d08ed9bcf6 100644 --- a/core/resources/src/commonMain/composeResources/values-srp/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-srp/strings.xml @@ -176,7 +176,6 @@ Неусаглашеност јавних кључева Шифровање јавним кључем - Дељени кључ Метрике сензора Окружење diff --git a/core/resources/src/commonMain/composeResources/values-sv/strings.xml b/core/resources/src/commonMain/composeResources/values-sv/strings.xml index 072336df0e..01af457c73 100644 --- a/core/resources/src/commonMain/composeResources/values-sv/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-sv/strings.xml @@ -424,8 +424,6 @@ Publik nyckel matchar inte Kryptering med Publik nyckel Direktmeddelanden använder den nya publika nyckelinfrastrukturen (PKI) för kryptering. - Delad nyckel - Endast kanalmeddelanden kan skickas/tas emot. Direkta meddelanden kräver funktionen Public Key Infrastructure i 2.5+ fast programvara. Miljövärden Miljö diff --git a/core/resources/src/commonMain/composeResources/values-tr/strings.xml b/core/resources/src/commonMain/composeResources/values-tr/strings.xml index e76ca2b933..7e6e2cab03 100644 --- a/core/resources/src/commonMain/composeResources/values-tr/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-tr/strings.xml @@ -193,7 +193,6 @@ Şifreleme etkin Genel Anahtar Uyuşmazlığı Genel Anahtar Şifrelemesi - Paylaşılan Anahtar Çevre Çevre metrikleri modülü etkin diff --git a/core/resources/src/commonMain/composeResources/values-uk/strings.xml b/core/resources/src/commonMain/composeResources/values-uk/strings.xml index 7958654b3d..8bfd66973f 100644 --- a/core/resources/src/commonMain/composeResources/values-uk/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-uk/strings.xml @@ -393,8 +393,6 @@ Публічний ключ не збігається із записаним ключем. Ви можете видалити вузол і дозволити йому обмінятися ключами знову, але це може свідчити про проблему з безпекою. Зв’яжіться з користувачем через інший довірений канал, щоб з’ясувати, чи була зміна ключа наслідком скидання до заводських налаштувань або іншої навмисної дії. Шифрування з відкритим ключем Для шифрування особистих повідомлень використовується нова система публічних ключів. - Спільний ключ - Доступні лише повідомлення в каналах. Прямі повідомлення потребують підтримки Pki, яка з'явилася у версіях прошивки 2.5+ та вище. Показники довкілля Середовище diff --git a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml index d692002f8c..8dff1c94af 100644 --- a/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml @@ -572,8 +572,6 @@ 公钥与输入的密钥不匹配。 您可以移除该节点并让它再次交换密钥，但这可能会出现密钥泄露问题。 请通过另一个受信任的频道来联系用户，以确定密钥更改是否由于出厂重置或其他故意操作。 公钥加密 私信消息正在使用新的公用钥匙加密。 - 共享密钥 - 只能发送/接收频道消息。私信需要2.5及以上版本固件中的公钥加密。 传感器指标 环境 diff --git a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml index 59d16c961e..8ec0b4811f 100644 --- a/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml +++ b/core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml @@ -429,8 +429,6 @@ 公開金鑰與先前記錄不符。您可以移除此節點並重新進行金鑰交換,但這可能代表有更嚴重的安全性問題。建議透過其他可靠的通訊方式聯繫該使用者,確認金鑰改變是否為重設裝置或其他有意的操作。 加密公鑰 私訊功能已改用新的公開金鑰基礎建設加密。 - 共用金鑰 - 目前只能使用頻道訊息，無法使用私訊功能。若要使用私訊功能，請將韌體更新至 2.5 以上版本。 環境計量資料 環境 diff --git a/docs/ar-rSA/user/nodes.md b/docs/ar-rSA/user/nodes.md index d149156f99..43f22af27d 100644 --- a/docs/ar-rSA/user/nodes.md +++ b/docs/ar-rSA/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/be-rBY/user/nodes.md b/docs/be-rBY/user/nodes.md index dc98fc85aa..9436e713ac 100644 --- a/docs/be-rBY/user/nodes.md +++ b/docs/be-rBY/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/bg-rBG/user/nodes.md b/docs/bg-rBG/user/nodes.md index 5890d0956d..fa4de24954 100644 --- a/docs/bg-rBG/user/nodes.md +++ b/docs/bg-rBG/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ca-rES/user/nodes.md b/docs/ca-rES/user/nodes.md index 451ea87a38..428fabaa09 100644 --- a/docs/ca-rES/user/nodes.md +++ b/docs/ca-rES/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/cs-rCZ/user/nodes.md b/docs/cs-rCZ/user/nodes.md index 052a125511..72f8d32aa0 100644 --- a/docs/cs-rCZ/user/nodes.md +++ b/docs/cs-rCZ/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/de-rDE/user/nodes.md b/docs/de-rDE/user/nodes.md index 3a3c78db81..7724075121 100644 --- a/docs/de-rDE/user/nodes.md +++ b/docs/de-rDE/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Symbol | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Symbol | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/el-rGR/user/nodes.md b/docs/el-rGR/user/nodes.md index 3b58a9a1b5..dab1aabde9 100644 --- a/docs/el-rGR/user/nodes.md +++ b/docs/el-rGR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/es-rES/user/nodes.md b/docs/es-rES/user/nodes.md index fb65f332bd..da267aeb64 100644 --- a/docs/es-rES/user/nodes.md +++ b/docs/es-rES/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/et-rEE/user/nodes.md b/docs/et-rEE/user/nodes.md index 5e0dc46e80..31bcbcfa29 100644 --- a/docs/et-rEE/user/nodes.md +++ b/docs/et-rEE/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Sõlmed kuvavad oma nime kõrval krüpteerimisoleku ikoone: -| Ikoon | Tähendus | -| --------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| 🔒 Lukustatud | Suhtlus kasutab PKI-d (avaliku võtme infrastruktuuri) – otsast lõpuni krüpteeritud kontrollitud identiteediga | -| 🔓 Lukust lahti | Suhtlus kasutab jagatud kanali PSK – krüpteeritud, kuid isikut pole individuaalselt kontrollitud | -| ⚠️ Ebakõla | Avaliku võtme mittevastavus — sõlme võti on viimasest nägemisest saadik muutunud (enne usaldamist uuri) | +| Ikoon | Tähendus | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Lukustatud | Suhtlus kasutab PKI-d (avaliku võtme infrastruktuuri) – otsast lõpuni krüpteeritud kontrollitud identiteediga | +| 🔓 Lukust lahti | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Ebakõla | Avaliku võtme mittevastavus — sõlme võti on viimasest nägemisest saadik muutunud (enne usaldamist uuri) | -> 💡 **Vihje:** PKI krüpteering (püsivara 2,5+) pakub tugevamat turvalisust kui kanali PSK, kuna igal sõlmel on unikaalne võtmepaar. Kui näed võtme mittevastavuse hoiatust, võib sõlm olla lähtestatud või ohustatud. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. Kui näed võtme mittevastavuse hoiatust, võib sõlm olla lähtestatud või ohustatud. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/fi-rFI/user/nodes.md b/docs/fi-rFI/user/nodes.md index 8b510f99c9..525771cac9 100644 --- a/docs/fi-rFI/user/nodes.md +++ b/docs/fi-rFI/user/nodes.md @@ -81,10 +81,10 @@ Radiot näyttävät nimensä vieressä salauksen tilaa kuvaavat kuvakkeet: | Kuvake | Merkitys | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 🔒 Lukittu | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | -| 🔓 Lukitsematon | Yhteys käyttää PKI:tä (julkisen avaimen infrastruktuuria) — päästä päähän salattu ja varmennetulla identiteetillä suojattu. | +| 🔓 Lukitsematon | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | | ⚠️ Ei täsmää | Julkinen avain ei täsmää — radion avain on muuttunut viime näkemän jälkeen (tutki ennen luottamista). | -> 💡 **Vinkki:** PKI-salaus (laiteohjelmisto 2.5+) tarjoaa vahvemman suojauksen kuin kanavan PSK-avain, koska jokaisella radiolla on oma yksilöllinen avainparinsa. Jos näet avaimen täsmäämättömyysvaroituksen, radio on voitu nollata tai sen tietoturva on voinut vaarantua. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. Jos näet avaimen täsmäämättömyysvaroituksen, radio on voitu nollata tai sen tietoturva on voinut vaarantua. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/fr-rCA/user/nodes.md b/docs/fr-rCA/user/nodes.md index 15bf20eb4f..7e978597d7 100644 --- a/docs/fr-rCA/user/nodes.md +++ b/docs/fr-rCA/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/fr-rFR/user/nodes.md b/docs/fr-rFR/user/nodes.md index 15bf20eb4f..7e978597d7 100644 --- a/docs/fr-rFR/user/nodes.md +++ b/docs/fr-rFR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ga-rIE/user/nodes.md b/docs/ga-rIE/user/nodes.md index 389877fa1c..3ee925d3a7 100644 --- a/docs/ga-rIE/user/nodes.md +++ b/docs/ga-rIE/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/gl-rES/user/nodes.md b/docs/gl-rES/user/nodes.md index aac33e4cba..dc3c343ba6 100644 --- a/docs/gl-rES/user/nodes.md +++ b/docs/gl-rES/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/hr-rHR/user/nodes.md b/docs/hr-rHR/user/nodes.md index 65aa810d67..b115f2a933 100644 --- a/docs/hr-rHR/user/nodes.md +++ b/docs/hr-rHR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ht-rHT/user/nodes.md b/docs/ht-rHT/user/nodes.md index a016873060..b336256149 100644 --- a/docs/ht-rHT/user/nodes.md +++ b/docs/ht-rHT/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/hu-rHU/user/nodes.md b/docs/hu-rHU/user/nodes.md index 0ff88c56c8..137fbc6c0c 100644 --- a/docs/hu-rHU/user/nodes.md +++ b/docs/hu-rHU/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/is-rIS/user/nodes.md b/docs/is-rIS/user/nodes.md index bcd00500b8..d9974f57f1 100644 --- a/docs/is-rIS/user/nodes.md +++ b/docs/is-rIS/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/it-rIT/user/nodes.md b/docs/it-rIT/user/nodes.md index 35521819a9..4f7d7242e4 100644 --- a/docs/it-rIT/user/nodes.md +++ b/docs/it-rIT/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/iw-rIL/user/nodes.md b/docs/iw-rIL/user/nodes.md index 72c3778b7b..207e726655 100644 --- a/docs/iw-rIL/user/nodes.md +++ b/docs/iw-rIL/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ja-rJP/user/nodes.md b/docs/ja-rJP/user/nodes.md index 2b3cfe684e..8784138188 100644 --- a/docs/ja-rJP/user/nodes.md +++ b/docs/ja-rJP/user/nodes.md @@ -78,13 +78,13 @@ There is no separate "away" tier. ノードは、名前の横に暗号化ステータスのアイコンを表示します： -| アイコン | 意味 | -| -------- | --------------------------------------------------- | -| 🔒 ロック | 通信は PKI（公開鍵基盤）を使用します。本人性が検証された、エンドツーエンドの暗号化です | -| 🔓 ロック解除 | 通信は共有チャンネルの PSK を使用します。暗号化されていますが、本人性は個別には検証されていません | -| ⚠️ 不一致 | 公開鍵の不一致。前回確認時からノードの鍵が変わっています（信頼する前に調べてください） | +| アイコン | 意味 | +| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 ロック | 通信は PKI（公開鍵基盤）を使用します。本人性が検証された、エンドツーエンドの暗号化です | +| 🔓 ロック解除 | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ 不一致 | 公開鍵の不一致。前回確認時からノードの鍵が変わっています（信頼する前に調べてください） | -> 💡 **ヒント：** PKI 暗号化（ファームウェア 2.5 以降）は、各ノードが固有の鍵ペアを持つため、チャンネル PSK より強力なセキュリティを提供します。 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。 +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。 To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ko-rKR/user/nodes.md b/docs/ko-rKR/user/nodes.md index 60455c5e98..9462d51e5a 100644 --- a/docs/ko-rKR/user/nodes.md +++ b/docs/ko-rKR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/lt-rLT/user/nodes.md b/docs/lt-rLT/user/nodes.md index 98256c1ad1..0c8bf2eb05 100644 --- a/docs/lt-rLT/user/nodes.md +++ b/docs/lt-rLT/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/nl-rNL/user/nodes.md b/docs/nl-rNL/user/nodes.md index 6c148d7305..2aee974ce8 100644 --- a/docs/nl-rNL/user/nodes.md +++ b/docs/nl-rNL/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/no-rNO/user/nodes.md b/docs/no-rNO/user/nodes.md index 914bdd4e24..215e3f09bf 100644 --- a/docs/no-rNO/user/nodes.md +++ b/docs/no-rNO/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/pl-rPL/user/nodes.md b/docs/pl-rPL/user/nodes.md index dba7206524..186903482d 100644 --- a/docs/pl-rPL/user/nodes.md +++ b/docs/pl-rPL/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/pt-rBR/user/nodes.md b/docs/pt-rBR/user/nodes.md index afe625d285..0ef88ed72f 100644 --- a/docs/pt-rBR/user/nodes.md +++ b/docs/pt-rBR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/pt-rPT/user/nodes.md b/docs/pt-rPT/user/nodes.md index efe84bff87..44c49242d4 100644 --- a/docs/pt-rPT/user/nodes.md +++ b/docs/pt-rPT/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ro-rRO/user/nodes.md b/docs/ro-rRO/user/nodes.md index 8a6f925e3a..39c58be04b 100644 --- a/docs/ro-rRO/user/nodes.md +++ b/docs/ro-rRO/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/ru-rRU/user/nodes.md b/docs/ru-rRU/user/nodes.md index 1d3f3accc2..8b27c10a54 100644 --- a/docs/ru-rRU/user/nodes.md +++ b/docs/ru-rRU/user/nodes.md @@ -78,13 +78,13 @@ There is no separate "away" tier. У нод рядом с именем отображаются значки статуса шифрования: -| Значок | Значение | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------- | -| 🔒 Заблокировано | Связь использует PKI (инфраструктуру публичных ключей) — сквозное шифрование с проверкой идентичности | -| 🔓 Разблокировано | Связь использует общий канал PSK — зашифровано, но личность не проверяется индивидуально | -| ⚠️ Несовпадение | Несовпадение открытого ключа — ключ ноды изменился с последнего раза (разберитесь, прежде чем доверять) | +| Значок | Значение | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Заблокировано | Связь использует PKI (инфраструктуру публичных ключей) — сквозное шифрование с проверкой идентичности | +| 🔓 Разблокировано | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Несовпадение | Несовпадение открытого ключа — ключ ноды изменился с последнего раза (разберитесь, прежде чем доверять) | -> 💡 **Совет:** Шифрование PKI (прошивка 2.5+) обеспечивает более надёжную защиту, чем общий PSK для канала, потому что у каждой ноды есть уникальная пара ключей. Если видишь предупреждение о несоответствии ключа, нода могла быть сброшена или скомпрометирована. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. Если видишь предупреждение о несоответствии ключа, нода могла быть сброшена или скомпрометирована. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/sk-rSK/user/nodes.md b/docs/sk-rSK/user/nodes.md index c2974e956d..a736dc7be2 100644 --- a/docs/sk-rSK/user/nodes.md +++ b/docs/sk-rSK/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/sl-rSI/user/nodes.md b/docs/sl-rSI/user/nodes.md index db87d3761d..fb6a88ea31 100644 --- a/docs/sl-rSI/user/nodes.md +++ b/docs/sl-rSI/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/sq-rAL/user/nodes.md b/docs/sq-rAL/user/nodes.md index 6b0538f61a..22d0aed113 100644 --- a/docs/sq-rAL/user/nodes.md +++ b/docs/sq-rAL/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/sr-rLatn/user/nodes.md b/docs/sr-rLatn/user/nodes.md index f25b8cf3e0..a1fec137de 100644 --- a/docs/sr-rLatn/user/nodes.md +++ b/docs/sr-rLatn/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Иконица | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Иконица | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/srp/user/nodes.md b/docs/srp/user/nodes.md index 082e67c91e..f70843b57e 100644 --- a/docs/srp/user/nodes.md +++ b/docs/srp/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Иконица | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Иконица | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/sv-rSE/user/nodes.md b/docs/sv-rSE/user/nodes.md index 3b208b3636..0ce0f3024b 100644 --- a/docs/sv-rSE/user/nodes.md +++ b/docs/sv-rSE/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/tr-rTR/user/nodes.md b/docs/tr-rTR/user/nodes.md index 4bd2500136..9aac4c7759 100644 --- a/docs/tr-rTR/user/nodes.md +++ b/docs/tr-rTR/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/uk-rUA/user/nodes.md b/docs/uk-rUA/user/nodes.md index 1c70df7954..cb76a87c64 100644 --- a/docs/uk-rUA/user/nodes.md +++ b/docs/uk-rUA/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/zh-rCN/user/nodes.md b/docs/zh-rCN/user/nodes.md index 96fac24a95..5388e6b5ce 100644 --- a/docs/zh-rCN/user/nodes.md +++ b/docs/zh-rCN/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| 图标 | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| 图标 | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it. diff --git a/docs/zh-rTW/user/nodes.md b/docs/zh-rTW/user/nodes.md index 8e403c3f08..6ace10e72f 100644 --- a/docs/zh-rTW/user/nodes.md +++ b/docs/zh-rTW/user/nodes.md @@ -78,13 +78,13 @@ Most users should keep the default **Client** role. Consider a different role wh Nodes display encryption status icons next to their name: -| Icon | Meaning | -| ----------- | ------------------------------------------------------------------------------------------------------------------- | -| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | -| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified | -| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | +| Icon | Meaning | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity | +| 🔓 Unlocked | No public key has been received for this node, so it cannot be direct messaged — use **Request User Info** on the node detail page to ask for one | +| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) | -> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised. +> 💡 **Tip:** Direct messages always use PKI, so the radio needs the other node's public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose **Remove**, and let the two radios exchange keys again the next time yours hears it.