[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: File [NETCONF-654] Steps to reproduce.odt     Zip Archive files654.zip    

 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:
1. private-key
2. public-key
3. host-key

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.

Generated at Wed Feb 07 20:15:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.