Synchronet now requires the libarchive development package (e.g. libarchive-dev on Debian-based Linux distros, for more info) to build successfully.

  1. 22 Mar, 2019 2 commits
    • rswindell's avatar
      Use default calling convention (__cdecl) for DLL funcs in Borland builds. · bf82a889
      rswindell authored
      Fix age-old bug with Borland/C++Builder built executables (Windows):
      to achieve compatibility with  the default __cdecl symbol naming rules of
      Visual C++, we were using __stdcall convention for DLL functions when
      building code with Borland/C++Builder tools and using the default (__cdecl)
      convention when building with Microsoft (Visual C++) tools. Although this
      allowed symbols to be located when linking, the calling convention mismatch
      caused a stack cleanup issue that very rarely manifested itself in a bug
      (e.g. exception of some kind in sbbsctrl.exe, usually). Mismatching
      the calling conventions was unintentional (I thought the default for MSVC
      DLL functions was __stdcall) - but since the calls to MSVC-Built DLL functions
      worked 99% of the time, I didn't realize there was an underlying issue. So I
      now work-around the DLL symbol naming mismatch using a command-line option (-a)
      passed to implib in src/sbbs3/ctrl/makelibs.bat
      I had previously worked-around exceptions when calling MSVC DLL functions in
      sbbsctrl.exe by calling the problematic DLL functions from a timer tick handler
      rather than a user control (e.g. button) event handler. Those work-arounds can
      now be removed.
      The erroneous "DLLCALL" definition design pattern was replicated (copy/pasted)
      to many other projects' header files in In the future, we may
      want to just remove all instances of *CALL since they now serve no purpose and
      appear as useless "Kruft" (but do allow us to more-easily globally change DLL
      function calling conventions if/when necessary in the future).
    • rswindell's avatar
  2. 20 Mar, 2019 3 commits
    • rswindell's avatar
      Added support for "lock" and "unlock" commands which will just lock (or unlock) · dc930b94
      rswindell authored
      the list database (sbbslist.json) for external processing/modification. When
      run via jsexec (as intended), jsexec will return 0 if the lock/unlock operation
      was successful, -1 otherwise. It would be wise to check the errorlevel/return
      value of jsexec for successful lock before operating on the list file.
    • rswindell's avatar
      Lock the database during the "backup" operation. · 3a08b966
      rswindell authored
      If the list is not sorted and the (capital) 'S' key is used (in browse mode),
      sort by the last column instead of the first.
    • rswindell's avatar
      Use a lock file (sbbslist.json.lock) to protect the database (sbbslist.json) · 806068b2
      rswindell authored
      from corruption during concurrent operations. Although the list file is not
      open shareable, I was observing corruption on Vertrauen when multiple sbbslist
      tasks (e.g. verification and maintenance) were running concurrently on
      different systems. The .lock file method is crude, but is working to protect
      the list from concurrent opens of any kind (read or write).
  3. 19 Mar, 2019 7 commits
  4. 16 Mar, 2019 2 commits
    • rswindell's avatar
      When adding a listfile (e.g. files.bbs), be a bit more strict: · e27d4a8f
      rswindell authored
      - filenames must begin with an alpha-numeric char. Might want to relax this in
        the future if it's a problem, but generally filenames on BBSes do begin with
        alpha-numeric characters and this will help us to identify an ignore
        "garbage" filenames in listfiles.
      - always check if the file actually exists, even when parsing the length of
        the file from the listfile. This will also help us to ignore garbage
      - also removed an inexplicable unpadfname() call. Filenames in file lists
        should *not* normally be padded (like "this    .txt") - so I'm not sure why
        this was in there. Perhaps for lists generated from filelist.exe (?). Anyway,
        out of an abundance of caution, removed it. Padded filenames are going away.
    • rswindell's avatar
      MsgBase.get_all_msg_headers() is now more tolerant of corrupted msg bases, · 6f4324d9
      rswindell authored
      or more specifically, if the index (.sid) file is of an unexpected size
      (too big or too small) handle that situation gracefully.
  5. 15 Mar, 2019 1 commit
    • rswindell's avatar
      Fix (or work-around?) ScalingFactor issue reported by ogg in fsxNet->FSX BBS: · dca11a6f
      rswindell authored
      The ScalingFactor would always (or usually) reset to 1 and have to be reset
      e.g. to 2, by resizing the window manually, every time SyncTERM was run.
      I found that by calling textmode() *after* setscaling() rather than before
      fixed this issue (at least in SDL mode on Ubuntu Linux). Another "fix" that
      worked inserting a small (100ms) delay between the calls to textmode() and
      setscaling() - so there appears to have been a race condition and calling
      setccaling() too soon after text mode() would fail to change the window
      size successfully. Reordering these calls seems to work 100% of the time
      without any additional delays. <shrug> Deuce would likely know "why" better
      than I.
  6. 13 Mar, 2019 5 commits
    • rswindell's avatar
      Rewind the msgbase index file before calling fread(). The fread() would · 0032f847
      rswindell authored
      fail if the current file pointer (offset) was not currently at the beginning
      of the file. So calling MsgBase.get_all_msg_headers() after previously calling
      any method that read/seeked the index would cause the reported error:
      "index read (xxxx) failed"
    • rswindell's avatar
      More strict FidoNet address detection (e.g. so IPv6 addresses aren't · 7f1471af
      rswindell authored
      detected as net_type NET_FIDO).
    • rswindell's avatar
      smb_netaddr_type() (exposed via JS as netaddr_type()) change: · d90ea2b8
      rswindell authored
      prior to rev 1.29 of this file (committed almost exactly one year ago), when
      called with any string that did not include an '@', would return NET_NONE (0).
      After rev 1.29, most strings that did not include an '@' would cause the
      function to return NET_QWK (4) - this was not intentional. The intention was
      that FidoNet addresses without an '@' would cause this function to return
      NET_FIDO (2) and I don't exactly remember why that change was made, but
      unfortunately, it wasn't made very well, so other invalid addresses would be
      detected as NET_QWK or NET_INTERNET or even NET_UNKNOWN.
      So before and after this commit:
      "" was NET_UNKNOWN, now NET_NONE
      "1" was NET_FIDO, now NET_FIDO
      "1x" was NET_INTERNET, now NET_NONE
      "1:103" was NET_FIDO, now NET_FIDO (this could use some work)
      "x" was NET_QWK, now NET_NONE
    • rswindell's avatar
      When extracting FILE_ID.DIZ/DESC.SDI, search through the exractable file · 8bd7cbdd
      rswindell authored
      types twice - first to see if one matches the requirements. If none match,
      then search again just for an extractor matching the file extension.
      Modernize the get_file_diz() function a little bit (e.g. return bool).
    • rswindell's avatar
      Moved the copy/pasted FILE_ID.DIZ/DESC.SDI code (3 times!?!) into its own · 3bc8ba86
      rswindell authored
      Constify mycmdstr() arguments.
      Removed trailing whitespaces.
      No functional changes expected by this commit.
  7. 10 Mar, 2019 1 commit
  8. 09 Mar, 2019 1 commit
  9. 08 Mar, 2019 1 commit
  10. 07 Mar, 2019 1 commit
    • deuce's avatar
      There appears to be data corruption in cryptlib if a private key is added · 211a2a1a
      deuce authored
      to a second thread before the first has the session set active.  Add calls
      to lock/unlock the certificate to prevent this.
      The better options is likely to have a function that adds the key and socket
      and sets the session active in one call and handles the locking internally.
      But I'm lazy, so we get the lock functions.
  11. 28 Feb, 2019 1 commit
    • rswindell's avatar
      Implement an (in-memory) Avatar cache - reducing the number of disk accesses · cb205ec3
      rswindell authored
      when using features that support avatars (e.g. reading msgs, listing files,
      listing BBSes in the BBS list).
      When used in the terminal server, the cache is located in bbs.mods.avatar_cache
      otherwise it's located in the scope of the load()'d library. Applications must
      use the lib's read() method to take advantage of the cache. The other lower
      level functions (e.g. read_localuser, read_netuser) by-pass the cache on read
      but do update the cache with the result. So, generally, avatars should be only
      loaded from disk one time during a session/logon.
  12. 21 Feb, 2019 4 commits
  13. 20 Feb, 2019 1 commit
    • rswindell's avatar
      Reversed course on the WM_QUOTE mode handling in sbbs_t::postmsg() · 57424543
      rswindell authored
      (JS bbs.post_msg()): If the WM_QUOTE mode flag is *not* set, then it will auto-
      create the quote file (quotes.txt) and add the WM_QUOTE mode bit before calling
      sbbs_t::writemsg(). So if existing JS scripts call bbs.post_msg(..., WM_QUOTE)
      with a custom-created quote file (e.g. with msg tails), that'll still work as
      before (e.g. DDMsgReader.js).
    and bbs.netmail() now support an optional reply_header_object
      argument which works like bbs.post_msg(). These methods (and the underlying
      C++ methods: sbbs_t::email(), netmail(), inetmail(), all auto-create the
      quote file now, when the WM_QUOTE mode flag is *not* set.
      The auto-created quotes.txt now includes the plain-text version of MIME-encoded
      the bbs.post_msg(), email(), and netmail() methods now all support reply
      header objects that came directly from bbs.get_msg_header() *or* copies of
      such header objects (but the auto-quoting feature won't work when supplied
      this type of header object). So if passed a header object returned from
      bbs.get_msg_header(), we can now use the message base (for auto-quoting) and
      the underlying msg storage directly (no JS parsing necessary). This is what
      the new js_GetMsgHeaderObjectPrivates() function is used for.
      js_ParseMsgHeaderObject() (and the underlying parse_header_object() function)
      now supports either an actual internally-generated msg header object (e.g.
      returned from bbs.get_msg_header()) or one that is a copy or hand-constructed.
      quotemsg() no longer tries to get a copy of the msg index/header. It shouldn't
      have to since we can now get to underlying msg storage in the js_msgbase.c
      via js_GetMsgHeaderObjectPrivates().
      quotemsg() now reads only the plain-text portion of MIME-encoded messages.
      As part of this effort, I modernized the method prototypes using default
      argument values (e.g. WM_NONE for wm_mode arguments) and removed some
      extraneous WM_EMAIL and WM_NETMAIL specifications (these wm_mode flags are
      automatically added by the sbbs_t::email() and *netmail() functions).
      savemsg() now *does* support reply-IDs/thread-linkage via the additional
      'remsg' argument (when non-NULL).
      Replaced some use of nulstr with NULL.
      Replaced more boilerplate SMB open code with calls to smb_open_sub().
  14. 19 Feb, 2019 9 commits
  15. 18 Feb, 2019 1 commit