I have two device names that are similar csshnp01 and sshnp01 the first is using the C daemon the second is using the Dart daemon which is also using a thurd atSign for policy.
When I try to connect to the csshnp01 i see a policy request from the sshnp01 device which I am not expecting as it should only be matching on device name before a policy check (I think).
Steps to reproduce
First set up two sshnpd daemons with device names as above and the sshnp01 deamon pointing to a policy atSign
Then sshnp to the csshnp01 device
And then see the policy trigger in the policy UI
Expected behavior
Only policy requests if the device name matches
Additional context
This is much easier to see if the C daemon is swicthed off.. I suspect it is nothing to do with the C code but the policy code on the Dart -p code not fully checking the device name.
Describe the bug
I have two device names that are similar
csshnp01
andsshnp01
the first is using the C daemon the second is using the Dart daemon which is also using a thurd atSign for policy. When I try to connect to thecsshnp01
i see a policy request from thesshnp01
device which I am not expecting as it should only be matching on device name before a policy check (I think).Steps to reproduce
sshnp01
deamon pointing to a policy atSigncsshnp01
deviceExpected behavior
Only policy requests if the device name matches
Additional context
This is much easier to see if the C daemon is swicthed off.. I suspect it is nothing to do with the C code but the policy code on the Dart -p code not fully checking the device name.