[NETCONF-654] change to the public key is not considered Created: 13/Jan/20 Updated: 03/Mar/22 Resolved: 03/Mar/22 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Manoj Chokka | Assignee: | Ivan Martiniak |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | netconf, netconf-callhome, pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Description |
|
Below is the scenario, There are three callhome devices added with the same host key and different unique ids. Once the device is disconnected and connected back after changing the host public key the device is connected. But that should not happen. This is a bug. |
| Comments |
| Comment by Ivan Martiniak [ 03/Mar/22 ] |
|
After deeper exploration, there are 3 keys in case of connection callhome device to ODL: 3. key is generated only from 1. not 1. and 2. Thus, when 2. is changed inside keystore of a device (can be even empty), it does not take effect for the creation of 3. Closing as "Cannot reproduce", feel free to reopen, if any suspicious behavior will be present and please provide more information. |