Repository navigation
Bug: --get security.adminKey responds in different formats to LoRa (--dest) and WiFi (--tcp) #956
Description
When one requests the admin key directly, the response is in base64.
meshtastic --tcp 192.168.1.200 --get security.admin_key
Connected to radio
security.admin_key: ['base64:vWKJ/ToM75NOFpMZ8g9B3Rc8zQYU+vvUEWUfAM9g+xQ=']
Completed getting preferences
When one requests the admin key as an admin command over LoRa, the response is an octal escape sequence
meshtastic --tcp $ATEIP --dest '!b03dbb38' --get security.admin_key
Connected to radio
Requesting current config from remote node (this can take a while).
security:
public_key: "\341\317*\305\230\026\207+\3703\364\302\211/\021\224<\313\371AlQ\201\326>L5\315\276\360\266\034"
private_key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
admin_key: "Ec\207\371\236\261\203^A\252L\222A\270\351\304\373\303t\321\010\247i>w\272`GJ\204\326i"
admin_key: "\275b\211\375:\014\357\223N\026\223\031\362\017A\335\027<\315\006\024\372\373\324\021e\037\000\317`\373\024"
serial_enabled: true
Activity
[-]Bug: --get security.adminKey responds in different formats to LoRa (--destin) and WiFi (--tcp)[/-][+]Bug: --get security.adminKey responds in different formats to LoRa (--dest) and WiFi (--tcp)[/+]