Python node isn't currently signed

Scripting
1

Hi,

Not sure if this is possible, but we run an airlocked system on circa 300 virtual desktops so all applications need to be added to an allow list. We are in the process of migrating to windows 11, we are currently testing all of the apps in our environment.

When placing a python node in the latest version for the first time, the runtime is installed into the user profile. The Python node is being blocked by our Airlock system, and we can’t verify through the publisher because it isn’t signed, is it possible to get a signed version on future updates for all of the python files?

This would hugely simplify our ability to allow this feature for our users.

I’ve attached also the airlock log also which lists everything that is currently being blocked in case that helps

image
image164×119 2.82 KB

export.1758268505.csv (43.5 KB)

image
image1920×1151 372 KB

3

@Ian_James Hello Ian. The CSV file that you shared is listing all .pyc files that are installed when Rhino 8 initializes and prepares the python 3 environment. These are installed with packages like parso, jedi, etc that are needed for the operation of script editor.

We can not sign these files as they belong to the publishing developers. An easier way is to have an exclusion for any .pyc files under C:\Users\ijames\.rhinocode\py39-rh8\site-support path if that is possible.