Repository navigation
clr throws (File is blocked (NTFS Security)) error when trying to AddReference on Mac #732
Description
Environment
- Pythonnet version: 2.4.0
- Python version: 3.5.4
- Operating System: Mac OS Sierra 10.12.1
Details
-
Describe what you were trying to get done.
I'm trying to add the reference of a dll to clr.
The problem is, when trying to add the reference, it throws an error message:
System.Exception: File is blocked (NTFS Security)
The same dll files work with pythonnet correctly in a windows environment.
I've sent the files to the mac from the pc via smb protocol. -
What commands did you run to trigger this issue?
import clr
clr.AddReference(r'TestLibrary.dll')- If there was a crash, please include the traceback here.
File "/Users/pfsteam/Desktop/XXXX/YYYY/ZZZZ/server/handler.py", line 76, in simulator_handler
clr.AddReference(r'TestLibrary.dll')
System.Exception: File is blocked (NTFS Security)
at Python.Runtime.CLRModule.AddReference (System.String name) [0x00053] in <839f97acd45d4def8bcdb1c7938a79c0>:0
at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0003b] in <2774478d59ae47bd8b8bfafb23c3364c>:0
Process finished with exit code 1
Activity
den-run-ai commentedon Sep 5, 2018
@davidanthoff are you able to load this dll on mac side without pythonnet, e.g. from powershell or scriptcs?
davidguaita commentedon Sep 7, 2018
Hi, @denfromufa thanks and sorry for the delay.
The library works when loading from mac powershell
The problem seems to be not the content of the library, but the path of the dll.
For instance,
works perfectly, but fails with
System.Exception: File is blocked (NTFS Security)error if I try to do:The path of the Python scripts is obviously
/Users/pfsteam/Desktop/XXXX/YYYYfilmor commentedon Sep 7, 2018
Just for completeness, you are also running from this path?
davidguaita commentedon Sep 7, 2018
Hi @filmor,
Yes, I'm running from this path
Zleep-Dogg commentedon Nov 2, 2018
I see the same issue on windows 7 with a DLL built internally in the company, and distributed via nuget
Python 3.7.1 (anaconda), pythonnet installed from git a couple of hours ago (pythonnet-2.4.0.dev0 according to pip install - I guess it must be this commit 3e4ebac - it' the first time I tried installing packages this way)
I believe this PR is what has introduced at least the error message: #655
So far I have been unable to find a format of the path that will allow me to add the reference to the DLL
I investigated a bit and found I could test this "security zone" from powershell ($name being the full path of the DLL):
That looks ok according to the change, so I am at a loss for what might be the actual issue here
den-run-ai commentedon Dec 6, 2018
@icetiger1974 any idea, multiple people (@davidguaita @Zleep-Dogg @amRsching) have issues with your PR?
den-run-ai commentedon Dec 6, 2018
@Zleep-Dogg can you check the security zones from python+pythonnet session like you did from powershell? It looks like
NoZoneshould be added to the accepted list. Powershell may have different settings.amRsching commentedon Dec 7, 2018
@denfromufa
I've run these several lines of codes you just posted. What I get is exactly the same as yours. (Python 3.7.0, Windows 10)
I guess this problem may be related to the Windows 10 new feature - "zone information".
The DLL files I want to use are all compressed in a zip file that I downloaded from the website.
Because the DLL file I want to add is extracted from the zip file, these DLL files may not have the corresponding "zone information", which may cause I can't successfully addReference on Windows 10.
Zleep-Dogg commentedon Dec 7, 2018
I get the same results in PS and python - here on windows 7.
Here is an example to share, not using the company DLL's, and using latest pythonnet from git cloning with pip (2.4.0.dev0 - I assume it must be d3ca2e8 though it's not really visible anywhere):
Oh, and the results are btw the same in python 3.7.1
den-run-ai commentedon Dec 7, 2018
crypt32.dllis not .NET dll.Zleep-Dogg commentedon Dec 7, 2018
Ah, sorry, just picked a random one that I figured should be on most people's PC.
But the result is exactly the same when I use the same method on a .NET dll provided by the "PC tool department", so I assume the errors arise before loading is actually attempted?
(Disclaimer: I am by no means fluent in .NET, C# or Windows, so I will easily hit pitfalls - I mostly work with C, assembly and a bit of python, and prefer working on linux, when not at work)
den-run-ai commentedon Dec 7, 2018
@Zleep-Dogg would you like to contribute a PR to fix this? Probably only add NoZone (-1) to the accepted security zone in pythonnet. Test it on your machine and no unit test is required (hard to reproduce).
Also if someone can document differences between Win7/10 security zones - that would be great. I have no idea about this.
Zleep-Dogg commentedon Dec 14, 2018
I won't have time this side of xmas, (the pythonnet work is sort of a side project to easily automate stuff otherwise only provided in GUI tools) - possibly after
DMT07 commentedon Feb 24, 2019
I am experiencing the same issue on Windows 7 with Python 3.7 and pythonnet 2.4.0.dev0. I am trying to use a DLL file that is being used by another program in Windows. When I open the 3rd party program it works fine. But when I try to add it in python,
clr.AddReference('MyDesired.dll')I get,
I have followed the SecurityZone heck above and I get the same NoZone:
Any suggestions? Or should I wait for a bug fix?
fix pythonnet#732 - add NoZone to allowed zones