Re: [Bug] setup regression #2

[Achim Gratz <Stromeko@nexgo.de>]

Jon Turney writes:
> On 03/10/2022 20:23, Achim Gratz wrote:
>> Jon Turney writes:
>>> This problem is with files created by setup, or by post-install scripts?
>> I think both, although the problematic symlinks were created through
>> alternatives.
>
> That's pretty baffling.

Even more baffling is that I have another installation that are
completely fine even with their Group now switched to Administrators.
The one syxstem where I've had the problems is a server version and
might have some GPO that affect thing that an admin user does.

> I don't see how any of those commits would change the ownership of
> files created by setup itself.

The ownership is still with the user that runs the install script,
however the group has changed.

> The only relevant change seems to be in "Defer setting group until
> after All Users/Just For Me is chosen", I've made
> nt_sec.resetPrimaryGroup() explicit, but that only happens for
> non-admin installs...

I think that setup was essentially treating the install as "for this
user only" since it was created and maintained by a script that can't
affect that option and the fact it was also in group Adminsitroators
didn't actually register until now.

The DACL on the server install changed from conferring access to "Everyone" to
just the install user and SYSTEM IIRC.  It doesn't do that on the
(non-domain) build machine at home that runs Win10 Pro.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables