Can NSIS's $TEMP value be over-ridden? -


i have customer using host intrusion protection , has set every user's temp folder not allow execution (c:\users\\appdata\local\temp). nsis extracts plugin dlls , own dlls folder below %temp%. problem nothing allow execute temp entire install fails. need know how tell nsis use different folder. work around can find edit temp , tmp values under registry key hcu\environment "%userprofile%\appdata\local\temp" c:\nsistemp. though works changing registry , putting not option. cannot redirect initplugindir effects plug-ins , not rest of nsis extracts (icons xml files etc...). ideas?s

you can set %tmp% in terminal/console window before running installer, there no need edit registry.

in nsis v3+ can use unsafestrcpy:

function .oninit unsafestrcpy $temp "c:\foo\bar" createdirectory "$temp" functionend 

the real problem security "solution", why preventing execution %temp% not other directories provide protection after bad guys find out restriction?


Comments

Popular posts from this blog

cakephp - simple blog with croogo -

How to group boxplot outliers in gnuplot -

bash - Performing variable substitution in a string -