Version: v4.11.3
Steps to reproduce:
- Open MeshMonitor and go to a MeshCore source
- Click "Add channel"
- Type
#bot as the channel name
- Note the secret shown
- Cancel and repeat 3 times
Expected behavior:
#bot should always produce the same 32-char hex key derived via SHA-256 of the name, and the key should update immediately when the name changes.
Actual behavior:
A different random key is shown each time. The key does not update when the channel name is changed. Three separate attempts produced three completely different keys for the same #bot name:
7d81cd9df13a152506ab1a36b5604b871e8fdf3de67a9d01cfcbda1a1961724ae16510550f7c984bea37d0005b28c4a1
This means the useEffect that should derive the key when the name starts with # is either not firing or is being overwritten by the initial random value.
This causes hashtag channels created in MeshMonitor to use a wrong key that does not match the key generated by the MeshCore app or other clients, making the channels incompatible.
Platform: Browser (Windows), MeshMonitor running in Docker on Linux
Version: v4.11.3
Steps to reproduce:
#botas the channel nameExpected behavior:
#botshould always produce the same 32-char hex key derived via SHA-256 of the name, and the key should update immediately when the name changes.Actual behavior:
A different random key is shown each time. The key does not update when the channel name is changed. Three separate attempts produced three completely different keys for the same
#botname:7d81cd9df13a152506ab1a36b5604b871e8fdf3de67a9d01cfcbda1a1961724ae16510550f7c984bea37d0005b28c4a1This means the
useEffectthat should derive the key when the name starts with#is either not firing or is being overwritten by the initial random value.This causes hashtag channels created in MeshMonitor to use a wrong key that does not match the key generated by the MeshCore app or other clients, making the channels incompatible.
Platform: Browser (Windows), MeshMonitor running in Docker on Linux