1. 03 Mar, 2017 1 commit
  2. 01 Mar, 2017 4 commits
    • rswindell's avatar
      +1 for NULL terminator. · 097a0825
      rswindell authored
      097a0825
    • rswindell's avatar
      Fix GCC warnings: · e95e0dae
      rswindell authored
      sbbsecho.h:186:7: warning: array æpktTypeStringListÆ assumed to have one element
      Warning: size of symbol `pktTypeStringList' changed from 8 in .../rechocfg.o
      e95e0dae
    • rswindell's avatar
      Packet Type-2e (FSC-39.4) support: · aace645d
      rswindell authored
      For packet creation, the only difference (from Type-2+) is with packets created
      from point nodes: the origNet field won't be set to 0xffff (as is the case with
      FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
      net (ala Squish) when configured for Type-2+ packet generation.
      When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
      reported as "2e" for valid "2+" packets. This is normal and expected when the
      originating node is not a point and the auxNet field is 0.
      The second set of orig/dest zone fields in a type 2e/2+ pkt header will
      now be used when importing if the old/QM orig/dest zone fields are 0.
      Also, the originating point field may now be imported even if the auxNet field
      is not used (origNet != 0xffff).
      
      New umask sbbsecho.ini configuration option (global), maybe used to over-ride
      the default *nix file creation mode mask (077), similar to sbbs.ini.
      aace645d
    • rswindell's avatar
      Changes in comments only: · dbaa70bc
      rswindell authored
      Use more formal terminology (e.g. "Type-2", not "type 2.0").
      dbaa70bc
  3. 27 Feb, 2017 2 commits
  4. 24 Feb, 2017 1 commit
    • rswindell's avatar
      2 Area-fix changes with regards to "pass-through areas": · 62f7e8ed
      rswindell authored
      - %RESCAN returns a different failure result if the requested echo is a
      pass-through area (cannot be rescanned)
      - %UNLINKED will return only the unlinked echoes even when an "additional
      echolist" is utliized and the linked areas are all pass-through (for Bill).
      62f7e8ed
  5. 21 Feb, 2017 2 commits
    • rswindell's avatar
      Fix potential crash (stack corruption) in qwk_route() reported by Hemo: · 2ff51deb
      rswindell authored
      If what appears to be a QWKnet addressed was passed, but the QWK-ID portion was
      exactly 9 characters, a 1-byte stack corruption would occur as the 10-char
      local variable (node) could be written with 11 chars (9-char QWK-ID, colon,
      null). The reported issue happend when attempting to send netmail to
      "hemo@ujointbbs" which is neither a valid Internet email address or a valid
      QWKnet address.
      2ff51deb
    • nightfox's avatar
      Version 0.16 beta: Added a main menu option to display poll stats - Lists the... · f9a83a63
      nightfox authored
      Version 0.16 beta: Added a main menu option to display poll stats - Lists the polls by highest number of votes (highest first), and for each one, lists the answer(s) with the highest number of votes (highest first).
      f9a83a63
  6. 20 Feb, 2017 1 commit
  7. 12 Feb, 2017 1 commit
  8. 10 Feb, 2017 1 commit
    • rswindell's avatar
      Added IPv4 CIDR notation support to all filter (*.can) files via the functions: · 26524908
      rswindell authored
      findstr() and findstr_in_list().
      This means that rather than listing an IP address range using the traditional
      wildcard characters (e.g. "192.168.1.*"), you could specify a subnet range
      using CIDR notation (e.g. "192.168.1.0/24").
      The '!' prefix is supported for CIDR match lines (for negated match results),
      but no other wildcard/match characters are (e.g. '^', '~', or '*').
      You can mix and match traditional match lines and CIDR match lines in the same
      filter file.
      IPv6 CIDR notation is not yet supported.
      26524908
  9. 09 Feb, 2017 1 commit
  10. 08 Feb, 2017 1 commit
  11. 06 Feb, 2017 2 commits
  12. 05 Feb, 2017 2 commits
  13. 29 Jan, 2017 1 commit
  14. 25 Jan, 2017 7 commits
  15. 22 Jan, 2017 3 commits
  16. 21 Jan, 2017 1 commit
  17. 20 Jan, 2017 1 commit
  18. 19 Jan, 2017 3 commits
  19. 17 Jan, 2017 2 commits
  20. 16 Jan, 2017 1 commit
  21. 15 Jan, 2017 2 commits