Author Topic: 2014 a pain in the...  (Read 15123 times)

0 Members and 1 Guest are viewing this topic.

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #30 on: April 03, 2013, 10:52:54 AM »
nothing i do makes this trustedpaths option work
my files simply wont load unless the paths are in the support file search path

This requires clarification... How have you been attempting to load your 'files' if not in SFSP?

Specific example would be helpful.

i have my files listed in the support path to make them work, if i list them in trustedpaths they dont work

That suggests that your 'load' call does not include the file path where your file is stored.

I haven't done enough testing to observe that TrustedPaths are, or are not included in LISP's Load function's ability to 'find' the file name parameter in SFSP if not specified, for example:

Code - Auto/Visual Lisp: [Select]
  1. (load "foo.lsp")

That said, and since this is not specified in the online help, I suspect that TrustedPaths is used as a second stage filter... Meaning that, in the example of a LISP (not sure what code file(s) you're wanting to load), the file path would need to be qualified in both SFSP (in order to be found), and TrustedPaths (for authorization).

Admittedly, speculation on my part... If someone knows better, please feel free to correct.

got it working, i uninstalled and reinstalled and its working so far, i think

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #31 on: April 03, 2013, 11:12:45 AM »
Now that you've re-installed and are experiencing different behavior, can you please test SecureLoad = 0 as RonJon suggested previously?

With SecureLoad = 0, I am unsure if TrustedPaths' value would result in different behavior if set to specific paths, or "" (empty string), or "." (period) per the docs.

I am trying to determine limitations (if any), as I do not have 2014 available at the moment (it's on another computer).

Cheers
"How we think determines what we do, and what we do determines what we get."

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #32 on: April 03, 2013, 11:15:15 AM »
ok so far what i got is
secureload 0 allows files to load without issues
and secureload 2 wont allow files to load at all unless they are listed in the trustedpath
and secureload 1 loads files in the trusted path but still gives a warning about the directory not being read only
« Last Edit: April 03, 2013, 11:52:22 AM by andrew_nao »

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #33 on: April 03, 2013, 11:17:43 AM »
ok so far what i got is
secureload 0 allows files to load without issues
and secureload 2 wont allow files to load at all
and secureload 1 loads files but gives a warning

Seems like all is functioning normally now, so there's no use for the Trust* LISP routines posted previously (which is a good thing, IMO).

Thanks for being willing / able to test that, andrew_nao. Much appreciated.
"How we think determines what we do, and what we do determines what we get."

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #34 on: April 03, 2013, 11:50:58 AM »
my script files dont work
in the same directory as my lisps.
the lisp work fine but not my script files...


*sigh*

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #35 on: April 03, 2013, 11:53:00 AM »
ok so far what i got is
secureload 0 allows files to load without issues
and secureload 2 wont allow files to load at all
and secureload 1 loads files but gives a warning

Seems like all is functioning normally now, so there's no use for the Trust* LISP routines posted previously (which is a good thing, IMO).

Thanks for being willing / able to test that, andrew_nao. Much appreciated.

i had to modify what i wont, i didnt explain it clearly enough

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #36 on: April 03, 2013, 11:53:46 AM »
my script files dont work
in the same directory as my lisps.
the lisp work fine but not my script files...


*sigh*

Not loading, or they're not working (i.e., an error, etc.)?

What are SecureLoad, and TrustedPaths set to (we've discussed several combinations)?
"How we think determines what we do, and what we do determines what we get."

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #37 on: April 03, 2013, 12:00:42 PM »
my script files dont work
in the same directory as my lisps.
the lisp work fine but not my script files...


*sigh*

Not loading, or they're not working (i.e., an error, etc.)?

What are SecureLoad, and TrustedPaths set to (we've discussed several combinations)?

got it working..

spell check
spell check
spell check
spell check


directory paths need to be in BOTH support file search path AND trustedpaths
and securemode set to 2
this will allow files to load from those paths only.

thank you everyone for your help

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #38 on: April 03, 2013, 12:14:23 PM »

got it working..

spell check
spell check
spell check
spell check

Glad you got it sorted.  :-D

directory paths need to be in BOTH support file search path AND trustedpaths
and securemode set to 2
this will allow files to load from those paths only.

Also, thanks for confirming my earlier speculation, on the nature of SFSP + TrustedPaths functions. :beer:
"How we think determines what we do, and what we do determines what we get."

ronjonp

  • Needs a day job
  • Posts: 7027
Re: 2014 a pain in the...
« Reply #39 on: April 03, 2013, 12:14:48 PM »
So essentially?

Code: [Select]
(_sfsp+ '("F:"        "F:\\ACAD\\acad2009"
  "F:\\ACAD\\acad2009\\lisp"        "F:\\ACAD\\acad2009\\menu"
  "F:\\ACAD\\acad2009\\menu\\bmp"      "F:\\ACAD\\acad2009\\dcl"
  "F:\\ACAD\\acad2009\\scripts"        "F:\\ACAD\\acad2009\\templates"
  "F:\\ACAD\\acad2009\\hatch pats"     "F:\\ACAD\\BLOCKS"
  "F:\\ACAD ARCHIVE"
)
)
(setvar 'trustedpaths (getenv "ACAD"))

Or sledghammer  :-P
Code: [Select]
(setvar 'secureload 0)

Windows 10 x64 - AutoCAD /C3D 2020

Custom Build PC

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #40 on: April 03, 2013, 12:24:21 PM »
So essentially?

Code: [Select]
(_sfsp+ '("F:"        "F:\\ACAD\\acad2009"
  "F:\\ACAD\\acad2009\\lisp"        "F:\\ACAD\\acad2009\\menu"
  "F:\\ACAD\\acad2009\\menu\\bmp"      "F:\\ACAD\\acad2009\\dcl"
  "F:\\ACAD\\acad2009\\scripts"        "F:\\ACAD\\acad2009\\templates"
  "F:\\ACAD\\acad2009\\hatch pats"     "F:\\ACAD\\BLOCKS"
  "F:\\ACAD ARCHIVE"
)
)
(setvar 'trustedpaths (getenv "ACAD"))

Or sledghammer  :-P
Code: [Select]
(setvar 'secureload 0)

dont even need all that just a F:\... works for ALL those paths
the "..." includes sub folders.

if the path is something OTHER then F:\ (in my case) then the path needs to be included

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #41 on: April 03, 2013, 12:25:14 PM »
So essentially?:

Code: [Select]
(setvar 'trustedpaths (getenv "ACAD"))

I argued this point to no fruitful end during Beta, as there were several discussions related to the new security mechanism... To my mind, it all stems back to the Profile's SFSP, as that (generally) is setup by one or more qualified individuals.

The premise that SFSP is not trusted is preposterous to my mind, and TrustedPaths *should* only be used to extend SFSP + implicitly trusted, OOTB folders (i.e., the now three ..\ApplicationPlugins\ folders, OOTB ..\Support\, etc.).

This formal 'rationale' that Autodesk has deemed network (not internet, but your office's own network) locations to be riskier than local disk folders that the user has full write-access to, again, it preposterous to my mind.

The user *should* have access to the application, and the enterprise *should* have access to the Autoloader from the network via SFSP (without the need for replication to local disk to implicitly trusted ..\ApplicationPlugins\).

... My $0.02
« Last Edit: April 03, 2013, 12:28:42 PM by BlackBox »
"How we think determines what we do, and what we do determines what we get."

BlackBox

  • King Gator
  • Posts: 3745
Re: 2014 a pain in the...
« Reply #42 on: April 03, 2013, 12:27:15 PM »
So essentially?

Code: [Select]
(_sfsp+ '("F:"        "F:\\ACAD\\acad2009"
  "F:\\ACAD\\acad2009\\lisp"        "F:\\ACAD\\acad2009\\menu"
  "F:\\ACAD\\acad2009\\menu\\bmp"      "F:\\ACAD\\acad2009\\dcl"
  "F:\\ACAD\\acad2009\\scripts"        "F:\\ACAD\\acad2009\\templates"
  "F:\\ACAD\\acad2009\\hatch pats"     "F:\\ACAD\\BLOCKS"
  "F:\\ACAD ARCHIVE"
)
)
(setvar 'trustedpaths (getenv "ACAD"))

Or sledghammer  :-P
Code: [Select]
(setvar 'secureload 0)

dont even need all that just a F:\... works for ALL those paths
the "..." includes sub folders.

if the path is something OTHER then F:\ (in my case) then the path needs to be included

Given the difference in SFSP + TrustedPaths you confirmed above, you should be able to use "F:\\..." as part of TrustedPaths, and keep "F:\\" out of your SFSP, and include the specific paths in your 'load' calling code... I believe that's what you're doing now, in any event.
"How we think determines what we do, and what we do determines what we get."

ronjonp

  • Needs a day job
  • Posts: 7027
Re: 2014 a pain in the...
« Reply #43 on: April 03, 2013, 12:35:32 PM »
Yup .. I was just using the example initially posted by the OP (placing all the paths in one list as Lee intended) :wink: The whole trusted paths thing seems a bit ridiculous to me ... but we're a small company.
« Last Edit: April 03, 2013, 12:45:36 PM by ronjonp »

Windows 10 x64 - AutoCAD /C3D 2020

Custom Build PC

andrew_nao

  • Swamp Rat
  • Posts: 566
Re: 2014 a pain in the...
« Reply #44 on: April 03, 2013, 01:15:45 PM »
all this could have been avoided if the documentation stated the paths need to be in BOTH places