• src/syncterm/conn_telnet.c

    From Deuc¿@VERT to Git commit to main/sbbs/master on Thu Mar 25 16:59:28 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/7b088502e28ed83749560b33
    Modified Files:
    src/syncterm/conn_telnet.c
    Log Message:
    telnet_interpret() can grow th input buffer by a byte.

    If a '\r' is the last thing in the previous receive buffer.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Deuc¿@VERT to Git commit to main/sbbs/master on Sun Dec 25 00:36:23 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/9db9df4a0f9a080a09e5d7a1
    Modified Files:
    src/syncterm/conn_telnet.c
    Log Message:
    Move telnet_expand() into SyncTERM proper.

    This allows ensuring we don't expand CRLF into CRLFLF. This is
    usually harmless, but there's no real need to put up with it in
    a program with a single thread using the expand function.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Mon Oct 28 15:46:43 2024
    https://gitlab.synchro.net/main/sbbs/-/commit/4376404234828ec45ef7d4db
    Modified Files:
    src/syncterm/conn_telnet.c
    Log Message:
    Ok, I'm convinced... initiate some telnet negotation

    - Attempt to suppress go aheads in both directions.
    - Attempt to set binary mode in both directions
    - Request the remote echos

    These express the assumptions that SyncTERM always makes, so it's
    a good idea to tell the remote this. For systems that don't like
    this, there is the Raw "protocol".

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net