Global settings for UpdateHostKeys and ForwardAgent

Core Shell Request Feature
1

Follow-up of WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

Thanks. I tried this option early without any changes in behavior, and there is no Global option for UpdateHostKeys. I'm not happy to edit each host settings - ssh-keygen -R host can be faster to resolve a problem.

Can you add a Global var UpdateHostKeys and Forward Agent to use as default?

2

UpdateHostKeys=ask works
but it's still require going to host settings and set this value (empty by default)

3

I split your post into a new topic so that we can track it as a feature request.

We may add a standalone preference tab for all advanced options, how fast it will be implemented depends on how many users vote it up.

Thank you for your suggestion :smiley:

4

It was by default in the you previous SSH client without any votes, I believe)

5

That's true, I agree. But Core Shell tries to keep consistent with OpenSSH, and for security reasons, OpenSSH disables ssh auth agent and reject all remote host which identification has changed.

Even we add a standalone preference tab for all advanced options eventually, user still have to set UpdateHostKeys and ForwardAgent explicitly, for security reasons of course.

6

It's not about security - but about usability.
Especially when you hide all useful info and display only
➤ [Abnormal Disconnect Sep 14, 2019 at 11:29:30 PM]
in the console.

You thinking user must discover a problem, but you can (you should) display a warning with available choose of possible actions.

7

Press ⌘ I (or select Shell -> Show Inspector from main menu) could reveal all hidden information.

image
image.png767×644 300 KB

8

Yes, I found this, but why it hidden?)
usability...

9

It was better with recent version

6
core shell Version- 1.6.6.png1932×502 61 KB

10

Print connection log into terminal is intuitive, but it has some drawbacks:

  1. The terminal could be full of nonsense logs while a host is unreachable (keep retrying every 3 seconds). You may find yourself depressed if you try to backtrack important output before disconnection.
  2. Colorless, hard to find critical information.
  3. If log level is set to DEBUG2 or lower, ssh actually emit logs constantly (items start with debug2 and debug3 in above screenshot). Debug log must be forced to be silent after host is connected, otherwise the terminal output will be polluted.

A standalone inspector popover solves above problems, and it is extendable, we can reveal more information users concerned by sort (without read through all the log items).