From 3252ed0f1357d55233f2d5cb50acf20dbb9160ed Mon Sep 17 00:00:00 2001 From: Kevin Hester Date: Mon, 5 Apr 2021 08:55:39 +0800 Subject: [PATCH] fix formatting --- docs/docs.md | 2 +- mesh.proto | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs.md b/docs/docs.md index c0e3e93..c8c5934 100644 --- a/docs/docs.md +++ b/docs/docs.md @@ -864,7 +864,7 @@ This message wraps a MeshPacket with extra metadata about the sender and how it | ----- | ---- | ----- | ----------- | | packet | [MeshPacket](#MeshPacket) | | The (probably encrypted) packet | | channel_id | [string](#string) | | The global channel ID it was sent on | -| gateway_id | [string](#string) | | The sending gateway. Can we use this to authenticate/prevent fake nodeid impersonation for senders? - i.e. use gateway/mesh id (which is authenticated) + local node id as the globally trusted nodenum | +| gateway_id | [string](#string) | | The sending gateway node ID. Can we use this to authenticate/prevent fake nodeid impersonation for senders? - i.e. use gateway/mesh id (which is authenticated) + local node id as the globally trusted nodenum | diff --git a/mesh.proto b/mesh.proto index 9224dca..9f975ae 100644 --- a/mesh.proto +++ b/mesh.proto @@ -240,7 +240,7 @@ message Routing { * The application layer service on the remote node received your request, but considered your request not authorized (i.e you did not * send the request on the required bound channel) */ - NOT_AUTHORIZED = 33; + NOT_AUTHORIZED = 33; } oneof variant {