1. 15 Apr, 2009 1 commit
    • Ben Avison's avatar
      Compatibility change for Microsoft security fix MS09-001. · 3ba506cd
      Ben Avison authored
      Detail:
        Security fix MS09-001 (detailed in Microsoft Knowledge base article KB958687)
        fixes some vulnerabilities in the SMB protocol which LanManFS uses. This
        highlighted an error in SMB_WriteRaw which reported zero data bytes but then
        supplied an offset to the non existant bytes: this is now faulted by Windows.
        As there are no data bytes, the offset should also be zero.
      Admin:
        Fix received from Rob Sprowson 2009-01-19.
      
      Version 2.31. Tagged as 'LanManFS-2_31'
      3ba506cd
  2. 16 Feb, 2004 1 commit
  3. 16 Jan, 2003 1 commit
    • Robert Sprowson's avatar
      Directory rename fixed - the mask being passed by the rename routine didn't... · 99169885
      Robert Sprowson authored
      Directory rename fixed - the mask being passed by the rename routine didn't have the ATTR_DIR bit set.Discovered this after reading lots of the spec which is also now included here in /doc.
      
      Copying files out of LanManFS filer "forgot" their filetype even though
      they appeared right in the filer,fixed.
      A stray debugging printf removed,along with one compiler warning.
      New sprites (yuck) to match !Omni.
      Reordered the shutdown in two places,first Omni_Shutdown bins the mounts
      lists which SMB_Shutdown uses.Second in NetBEUI mode the announcement that
      a protocol has terminated goes *after* the shutdown - otherwise you sit
      around for about 20s wondering where the link has gone.
      
      Version 2.25. Tagged as 'LanManFS-2_25'
      99169885
  4. 09 Jan, 2001 1 commit
    • Stewart Brodie's avatar
      Fixed bug in parsing of the protocol negotiation. · 4b49606e
      Stewart Brodie authored
      Detail:
        The wrong bit was being checked to see if we were using the extended
          security model (CAP_EXTENDED_SECURITY).  Thus the wrong format was
          being used in SMBsesssetup, which meant that we couldn't connect
          to Windows 2000.
        Much better debugging added to the name resolution code - this helped
          diagnose the faulty photocopier problem and is left in case anything
          like that happens again!
      Admin:
        Tested - I can now connect to Win 2000 shares.
      
      Version 2.17. Tagged as 'LanManFS-2_17'
      4b49606e
  5. 08 Aug, 2000 1 commit
    • Stewart Brodie's avatar
      Fixed machine stiff if connection left idle too long. · 4fc58c21
      Stewart Brodie authored
      Detail:
        SVC stack overflow occurred due to the recursive method used to
          discard the idle-out prevention responses.  This no longer
          happens.
        Fixed a bit of debugging which caused data aborts!
        Optimised a select() call to pass s + 1 as the first parameter to
          save Internet time in processing the fd_set.
      Admin:
        Tested on desktop build, with the idle timers set to send idle outs
          every second (so we don't have to wait 100 hours for the problem
          to occur).  No longer get problems with the machine stiffing.
      
      
      Version 2.12. Tagged as 'LanManFS-2_12'
      4fc58c21
  6. 04 Apr, 2000 1 commit
    • Stewart Brodie's avatar
      Fixed use of uninitialised pointer. · 01a3f774
      Stewart Brodie authored
        Now doesn't require that the !ArmBoot object is a directory
      Detail:
        The code in Omni.c was carefully checking that !ARMBOOT existed
          before attempting to run the boot file.  Unfortunately, it was
          using a method which bypassed the filename resolution (that does
          the ,xxx filetype name mapping), so it did not find the new Obey
          file in the 400 series baseline.  The check has been removed.
        The code in SMB.c was being caught out on an uninitialised variable
          usage when the attribute cache already held details of the object
          being sought.  The variable would have been initialised on a non-
          cached lookup, but the special case of booting a machine via LanManFS
          manages to get a cached lookup without having run through the routine
          before, resulting in a strcpy() with a destination of 0.
      Admin:
        Tested on Risc PC.
        Fixes fault 1511 (STB-400 Generic)
      
      Version 2.11. Tagged as 'LanManFS-2_11'
      01a3f774
  7. 21 Jan, 2000 1 commit
    • Stewart Brodie's avatar
      More tolerance has been added of files found on the remote server which have unexpected extensions. · 36543191
      Stewart Brodie authored
      Detail:
        LanManFS does not like it if you create (independently, using a PC or
          otherwise) files with names like "myfile,fff" which you intend to
          be displayed as files with type &FFF (ie. Text) on a RISC OS machine.
          If you tried to access the file for reading it, such as loading it
          into an editor, that worked due to the name matching resolution.
          However, any attempt to update the file caused LanManFS to attempt
          to write the file without the extension and not notice that a file
          with a ,fff extension already existed (Text files are special cased
          in the current implementation of name translation - see LanManFS
          Functional Specification for details and rationale).  Attempts to
          save typically succeed (giving you two files: myfile and myfile,fff)
          but generate "Operation not permitted" or such like.  This stemmed
          from the attempt being made by LanManFS to rename a file to the same
          name.  SMB_Rename now traps that and tells its caller that the rename
          succeeded.  The Xlate.c code now indicates correctly that the filename
          extension has been altered when a ,fff extension has to be chopped off.
      Admin:
        Tested briefly on desktop build against art-work's SAMBA server.
        Bug reported by TopCat engineers.
      
      Version 2.10. Tagged as 'LanManFS-2_10'
      36543191
  8. 29 Apr, 1999 1 commit
    • Stewart Brodie's avatar
      Now uses DebugLib. · 6ce2ce71
      Stewart Brodie authored
        Fixed search handle haemorrhaging.
      Detail:
        The directory lookup routines cached directory search handles to avoid
          hammering the server with repeated requests to open directories.
          Unfortunately, it was possible for these to be forgotten without
          being freed up leading to resource loss at the server end.  Eventually,
          the server gives up servicing you and reports errors.  This will only
          occur once a significant number of accesses have been performed (the
          number depends entirely on server configuration).  This leak is now
          fixed.
      Admin:
        Tested against Cerium - debug reports that no handles are being leaked.
      
      Version 2.07. Tagged as 'LanManFS-2_07'
      6ce2ce71
  9. 09 Mar, 1999 1 commit
    • Stewart Brodie's avatar
      Changed idle-out strategy. · feb9328e
      Stewart Brodie authored
        Introduced new error message for re-entrancy prevention trap to use.
      Detail:
        When 'pinging' an SMB server, LanManFS does not wait for any response
          but the response reading routine knows to just throw away any old
          SMBchkpth responses that it gets and try reading again.
        Re-entrancy trap now has its own error "LanManFS in use" &1663E, which
          means you no longer see "!Armboot files nested too deeply" which is
          confusing.  The only way you can provoke this message is if you use
          Alt-Break whilst the NetBIOS/IP code is executing.  The error plays
          the same part as "FileCore in use" does for FileCore.
      Admin:
        Verified module still works and the anti idle-out features still work.
      
      Version 2.04. Tagged as 'LanManFS-2_04'
      feb9328e
  10. 18 Feb, 1999 1 commit
    • Stewart Brodie's avatar
      Protocol negotiated features need to be per-server, not per-share. · 91cb8981
      Stewart Brodie authored
      Detail:
        Long filename flag tarnsferred to be a server property rather than
          a share property, otherwise subsequent shares to the same server
          do not get long filenames (because the subsequent shares don't
          have to go through the connection negotiation phase)
      Admin:
        Tested on by mounting lots of drives through desktop Omni frontend.
      
      Version 2.02. Tagged as 'LanManFS-2_02'
      91cb8981
  11. 16 Feb, 1999 1 commit
    • Stewart Brodie's avatar
      Support for long filename. · d49e6981
      Stewart Brodie authored
        Support for spaces in machine names.
        Merge of sbrodie_LanManFS_dev branch to trunk.
      Detail:
        LanManFS 2.00 supports the "NT LM 0.12" protocol, enabling it to
          use long filenames on mounted shares.
      Admin:
        Supporting documentation:
          1215,256/FS: LanManFS Software Functional Specification.
        Same as LanManFS-1_87_1_1_1_1_2_13.
      
      Version 2.00. Tagged as 'LanManFS-2_00'
      d49e6981
  12. 03 Dec, 1998 1 commit