1. Forum
  2. Fsxnet Message
  3. fsx Network ops/Planning

  • 21:1/100 "Warning: remote set UNSECURE session"

    From Oli@21:3/102 to All on Friday, May 21, 2021 12:11:48
    + 12:06 [1936] call to 21:1/100@fsxnet
    + 12:06 [1936] outgoing session with net1.fsxnet.nz:24556 [...]
    [...]
    - 12:06 [1936] SYS Agency + Risa HUB
    [...]
    + 12:06 [1936] Remote has 0b of mail and 0b of files for us
    - 12:06 [1936] OPT EXTCMD GZ BZ2
    + 12:06 [1936] Remote supports EXTCMD mode
    + 12:06 [1936] Remote supports GZ mode
    + 12:06 [1936] Remote supports BZ2 mode
    ? 12:06 [1936] Warning: remote set UNSECURE session
    ^^^^^^^^
    + 12:06 [1936] pwd protected session (MD5)
    + 12:06 [1936] done (to 21:1/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))

    Why doesn't 21:1/100 offer an CRYPT OPT?

    ---
    * Origin: . (21:3/102)
  • From Oli@21:3/102 to Oli on Saturday, May 22, 2021 08:33:36
    Did someone suggest to use the -r parameter with binkd? That would explain it:

    usage: binkd [-CcDipqrsvmh] [-P node] config
    -D run as daemon
    -C reload on config change
    [...]
    -r disable crypt traffic


    Oli wrote (2021-05-21):

    + 12:06 [1936] call to 21:1/100@fsxnet
    + 12:06 [1936] outgoing session with net1.fsxnet.nz:24556 [...]
    [...]
    - 12:06 [1936] SYS Agency + Risa HUB
    [...]
    + 12:06 [1936] Remote has 0b of mail and 0b of files for us
    - 12:06 [1936] OPT EXTCMD GZ BZ2
    + 12:06 [1936] Remote supports EXTCMD mode
    + 12:06 [1936] Remote supports GZ mode
    + 12:06 [1936] Remote supports BZ2 mode
    ? 12:06 [1936] Warning: remote set UNSECURE session
    ^^^^^^^^
    + 12:06 [1936] pwd protected session (MD5)
    + 12:06 [1936] done (to 21:1/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))

    Why doesn't 21:1/100 offer an CRYPT OPT?

    ---
    * Origin: . (21:3/102)

    ---
    * Origin: . (21:3/102)