Skip to content
Snippets Groups Projects
Select Git revision
  • 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
  • new_user_dat
  • 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

logonlist_lib.js

Blame
    • Rob Swindell's avatar
      16c5298f
      Log the current connection protocol as a separate property in logon.jsonl · 16c5298f
      Rob Swindell authored
      Accession reported that (sometimes?) his NNTP logins show up in his
      logon.jsonl files. This is most likely just a race condition when logging
      in close to the same time with multiple protocols (e.g. Telnet and NNTP
      in this case). So, let's log the client.protocol as a separate JSON property
      and not require on the user.connection property (which is overwritten for
      *every* login, for almost all connection/server types, not just the terminal
      server). The client.protocol is always correct for the current session running
      the script.
      
      An NNTP login should never appear in the logon.json file.
      16c5298f
      History
      Log the current connection protocol as a separate property in logon.jsonl
      Rob Swindell authored
      Accession reported that (sometimes?) his NNTP logins show up in his
      logon.jsonl files. This is most likely just a race condition when logging
      in close to the same time with multiple protocols (e.g. Telnet and NNTP
      in this case). So, let's log the client.protocol as a separate JSON property
      and not require on the user.connection property (which is overwritten for
      *every* login, for almost all connection/server types, not just the terminal
      server). The client.protocol is always correct for the current session running
      the script.
      
      An NNTP login should never appear in the logon.json file.