octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60912] Installing with installer corrupts per


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #60912] Installing with installer corrupts permissions on temporary directory (temp / tmp)
Date: Mon, 12 Jul 2021 17:39:30 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #1, bug #60912 (project octave):

Quite an odd story.

Having poked a little in the Windows installer creation scripts, I fail to see
how the Octave installer can change permissions of temp directories.
As Octave as been installed on probably many thousands of Windows systems and
you are the very first person to mention just these specific issues, I'm
rather inclined to think that there were already other issues in your system
that merely got uncovered, not induced, by the Octave installer.
Maybe even any installer might induce them - can you try to install some other
SW and see if you get similar problems? Preferably ones that also use NSIS
installer SW.

Some notes about what you wrote:
* Only in Windows Home edition the normal user has "some" *potential* admin
credentials - nowadays also Microsoft understands baseline security so normal
users never run with admin privileges anymore unless they click on some
security popup (the notorious UAC thing).
* I've seen the "rules in invalid order" myself several times (IIRC think it's
"access permissions" rather than "rules") but that was when there were other
issues with the NTFS volume in question. Oh and I couldn't get those
"repaired" either - probably higher credentials than "administrator" are
required, or starting the system in Safe mode.
* (Maybe I didn't understand your description properly?) It's a very bad idea
to fiddle with or in the system TEMP directory in the first place, let alone
move it around. That directory is for system operation, not for mortal users.
* I'm curious how you change your personal TEMP and TMP directory, other than
by temporarily adapting the environment settings in a powershell or CMD
window. Since a few Win10 releases only the SYSTEM and Administrator "TEMP" en
"TMP" environment settings can be changed; the cause is that the pertinent
system setting popup only applies to the user logged in for that popup and as
that popup can only be reached as admin there's no way to change it for
ordinary users anymore.

Maybe other Windows devs can chime in here?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60912>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]