Skip to content
Snippets Groups Projects
Select Git revision
  • dd_area_choosers_common_refactor
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • 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

sbbs

  • Clone with SSH
  • Clone with HTTPS
  • Rob Swindell (on Windows 11)'s avatar
    Rob Swindell authored
    Before this change, we'd always request a return to Telnet NVT (turn off
    binary-TX in both directions) after any file transfer. So although a Telnet
    session might be negotiated into binary mode shortly after connection
    (e.g., using "telnet -8"), it would be reverted back to NVT mode after any
    file transfer.
    
    The request to turn off remote binary-TX after executing external programs
    didn't actually accomplish anything since we track the Telnet option states
    internally and don't send redundant requests (e.g. the change into a mode
    we're already in). External programs aren't expected to send Telnet requests
    anyway, so I think this was some holdover from early days of stp/sexyz
    development.
    51c917d0
    History
    Name Last commit Last update