Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • dd_msg_reader_use_dd_msg_area_chooser_and_area_sort_update
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

ssh.c

Blame
    • Deucе's avatar
      2c036f74
      Allow retrying SSH client auth. · 2c036f74
      Deucе authored
      If you initially try private key auth for example, allow retrying
      with password auth and vice-versa.  This is needed for reasonable
      fallback from private-key auth since we don't know in advance
      which will work, and we don't want to disconnect an reconnect.
      
      This takes the guardrails of adding a password.  Previously, it was
      ensured that a password was always added immediately after a username.
      This is to ensure when using the server for example and stuffing a
      list full of all the user/pw pairs, each pw goes with a user.
      
      Instead of returning an error, this now allows adding passwords
      without a corrsponding user that won't be used, and there will be
      no indication of why.
      
      Death Star mode for this feature is better than not having fallback
      in my opinion.
      2c036f74
      History
      Allow retrying SSH client auth.
      Deucе authored
      If you initially try private key auth for example, allow retrying
      with password auth and vice-versa.  This is needed for reasonable
      fallback from private-key auth since we don't know in advance
      which will work, and we don't want to disconnect an reconnect.
      
      This takes the guardrails of adding a password.  Previously, it was
      ensured that a password was always added immediately after a username.
      This is to ensure when using the server for example and stuffing a
      list full of all the user/pw pairs, each pw goes with a user.
      
      Instead of returning an error, this now allows adding passwords
      without a corrsponding user that won't be used, and there will be
      no indication of why.
      
      Death Star mode for this feature is better than not having fallback
      in my opinion.