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
It appear that Blink will use key-based authentication only if this is requested explicitly with the -i options for SSH, respectively -I for mosh. This is different from how mosh/ssh work on my laptop, where it tries all available keys for authentication when ssh/mosh is invoked without options. Blink should either behave in the same way, or document the need to use -i/-I explicitly.
Also, it would seem feasible to add an option the the Key configuration for setting a "default" key, or "try all keys". In addition, or alternatively, a Hosts section in the config (to be implemented) could associate specific keys with specific hosts.
The text was updated successfully, but these errors were encountered:
It appear that Blink will use key-based authentication only if this is requested explicitly with the
-i
options for SSH, respectively-I
for mosh. This is different from how mosh/ssh work on my laptop, where it tries all available keys for authentication when ssh/mosh is invoked without options. Blink should either behave in the same way, or document the need to use-i
/-I
explicitly.Also, it would seem feasible to add an option the the Key configuration for setting a "default" key, or "try all keys". In addition, or alternatively, a Hosts section in the config (to be implemented) could associate specific keys with specific hosts.
The text was updated successfully, but these errors were encountered: