LabVIEW 2021 Public Beta

cancel
Showing results for 
Search instead for 
Did you mean: 

File access settings wrong.

./instr.lib/Agilent 34401/Private/Extended User Data.ctl has execute permission

many html files have execute permission

many mnu files have execute permission

many plist files have execute permission

a few so files have execute permission

etc. etc.

Many resource and distributed instr.lib files are world writable  (bad security at most admin writeable)

Hopefully someone will go over the distribution with a security script?  I usually run my own but YMMV.

BUG: 1042783

LabVIEW ChampionLabVIEW Channel Wires

0 Kudos
Message 1 of 2
(1,235 Views)

And just found that many settings are too restrictive.  For example it is impossible to use VIPM with the default settings even as an administrator.

 

The group should be set for admin for **AT LEAST** the following folders:

 

User.lib

menus

examples

vi.lib/addons

 

In general in setting up security for the LabVIEW installation I make the whole structure writeable by the admin group, just not standard users.  Assume that an admin can do anything anyway.

LabVIEW ChampionLabVIEW Channel Wires

0 Kudos
Message 2 of 2
(1,186 Views)