1. 21 Jan, 2021 2 commits
    • Rob Swindell's avatar
      Support single-part MIME-encoded messages in SMBLIB · c90ba307
      Rob Swindell authored
      This involved the removal of the content-transfer-decoding feature of the SMTP mail server since we need single-part MIME-attached file contents to be stored in their original encoded form (e.g. base64-encoded) and not in binary, for the message body text (where NULs aren't allowed, CR/LF is appended, etc).
      I accidentally made this change to smbtxt.c in the new_file_base branch and then copied over here, so there's some unrelated innocuous changes (comment header, removal of SMBCALL) that hopefully won't cause a merge conflict later.
      I don't actually receive single-part MIME attached files, so depending on others (e.g. Nelgin and Dream Master) to test for me.
    • Rob Swindell's avatar
      Clean-up MIME-Decoded plain-text format message · f039b2aa
      Rob Swindell authored
      Don't display at all if smb_getplaintext() returns a blank string.
      Don't display "(null)" if there's no text sub-type.
  2. 20 Jan, 2021 2 commits
  3. 19 Jan, 2021 1 commit
  4. 18 Jan, 2021 10 commits
  5. 17 Jan, 2021 4 commits
  6. 16 Jan, 2021 1 commit
    • Rob Swindell's avatar
      Fix js.exec() returned nul" unless exit() was called explicitly · da7c67c9
      Rob Swindell authored
      Don't use the "exit_code" property value as the return value of js.exec() unless it's a number. As reported by mlong (thanks).
      Also, "exit_code" was being set to null (instead of void/undefined) in js_PrepareToExecute(). I think this was just an oversight or typo by Deuce from his commit of 5 years ago (f3256d81). Since we're comparing exit_code with JSVAL_VOID in other places to determine if it was actually set, this appears to be a long standing bug.
  7. 15 Jan, 2021 2 commits
  8. 14 Jan, 2021 3 commits
  9. 13 Jan, 2021 3 commits
  10. 12 Jan, 2021 3 commits
  11. 11 Jan, 2021 9 commits