You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to work together on this. There's an issue where if there's two+ keys with different algos, the user will be prompted to clear bad keys two+ times until the old keys are gone. We need to record that target's IP / hostname in the job, and update the backend to remove all keys for that bad target. For the front end, we need to just change the job data to something like bad_target=192.168.12.1.
Related to #706 because of the 1+ key issue. A patch will be made to collect all related keys when given a target (i.e., IP, short name, full name, short name with network ID).
If you try to initialize a host and there's a bad key, you clear the key, and try to connect a second time, the UI hangs.
The text was updated successfully, but these errors were encountered: