windows: making library loading work after SetDefaultDllDirectories() call (#1413)
          #1614
        
          
      
      
        
          +7
        
        
          −3
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
When a client doesn't specify open options, JNA defaults to
LOAD_WITH_ALTERED_SEARCH_PATH(dispatch.c#L54). According toLoadLibraryExdocumentation, this results in an undefined behavior when a library name is given as a relative path.In a "normal" mode, this is not a problem: Windows just ignores the flag and carries on, but if an application tries to improve DLL loading security and restricts the DLL search path by calling
SetDefaultDllDirectories()(docs), callingLoadLibraryEx(relative_path, ..., LOAD_WITH_ALTERED_SEARCH_PATH)results inERROR_INVALID_PARAMETER.A simple reproducer in C, just in case:
The PR fixes the issue by setting default open options to
0when a relative path is specified.