topic Re: Inconsistent SECURELOAD Behavior in Visual LISP, AutoLISP and General Customization Forum

Inconsistent SECURELOAD Behavior

David_Robison — Fri, 01 Jul 2016 17:56:32 GMT

We are seeing inconsistent behavior with the SECURELOAD system variable.

For our add-in, we have the user load a VLX using APPLOAD. Typically SECURELOAD is set to the default value of 1. Most times, the user gets the security dialog asking if they want to load our VLX or not. They are able to answer "yes" and everything proceeds smoothly.

Some times, nothing happens. The VLX is not loaded and they do not get any warning or message about why. On the command line it says it is unable to load the VLX. We have them change SECURELOAD to 0 and then are able to load the VLX.

I am trying to figure out why we get different behavior with seemingly similar settings. Is there another system variable that has an impact on how SECURELOAD works?

Re: Inconsistent SECURELOAD Behavior

rkmcswain — Fri, 01 Jul 2016 18:16:29 GMT

It also evaluates the paths stored in Options (or accessible via the SECURITYOPTIONS command)

If the file is in a path included here, then no prompting will occur and the file will be loaded.

Also, if AutoCAD is in safe mode, no add-ons are loaded regardless of anything else.

Do you know about SECURELOAD = 2 vs 1?

Re: Inconsistent SECURELOAD Behavior

David_Robison — Fri, 01 Jul 2016 18:52:37 GMT

The add-in eventually adds its path to the "Trusted Locations" so the user doesn't continue to get this warning regardless of the SECURELOAD setting.

I am aware of 1 vs 2. I've never actually seen it set to 2 on a user's computer. The behavior I have seen is always with it set to 1.

Re: Inconsistent SECURELOAD Behavior

Ranjit_Singh — Fri, 01 Jul 2016 18:54:04 GMT

with secureload set to 1, vlx should load without warning, only if the vlx is located in trusted paths. If it is not in a trusted path then there will be a prompt. So in your case vlx is not located in a trusted path. Also, with 2 you will not get a message. So, sounds like the machines where you don't get a message the secureload is set to 2.

Both the situations you describe will happen when the file is not located in trusted location. Either move it to a trusted location or set secureload to 0 on all machines.

Re: Inconsistent SECURELOAD Behavior

JamesMaeding — Fri, 01 Jul 2016 20:53:03 GMT

Has anyone ever had a malicious anything try to load besides the good (bad) old "acaddoc.lsp" in same folder as a dwg?