mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-11-12 16:44:20 -08:00
Clarified that managed mode isn't required for admin control (#1532)
* Clarified that managed mode isn't required for admin control Clarified that managed mode isn't required for admin control. Also clarified the wording around admin control/legacy admin channel. * Update security.mdx Reworded per the comments * Update security.mdx * clarified text * clarified firmware versions * Adopted pdxlocs wording. --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com>
This commit is contained in:
parent
659ba39192
commit
9b5ffa3629
|
@ -34,7 +34,9 @@ The public key(s) authorized to send administrative messages to this node. Only
|
|||
|
||||
Acceptable values: `true` or `false`
|
||||
|
||||
Enabling Managed Mode restricts access to all radio configurations via client applications. Radio configurations will only be accessible through the Admin channel. Ensure the Admin channel is functioning properly before enabling this mode to avoid being locked out.
|
||||
Enabling Managed Mode blocks client applications from accessing all radio configurations. Once enabled, radio configurations can only be accessed through PKC Remote Admin messages with firmware version 2.5+ or the legacy Admin channel with firmware prior to version 2.5. However, this setting is not required for remote node administration.
|
||||
|
||||
Before enabling Managed Mode, verify that the node can be controlled via Remote Admin or legacy Admin channel, and that all functions are working properly to prevent being locked out.
|
||||
|
||||
### Serial Console
|
||||
|
||||
|
@ -121,7 +123,7 @@ meshtastic --set security.debug_log_api_enabled true
|
|||
|
||||
#### Web
|
||||
|
||||
All Security config options are available in the Web client.
|
||||
ALL Security config options are available in the Web client, but at present only 1 Remote Admin public key can be set.
|
||||
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
|
Loading…
Reference in a new issue