> > > > When compiling MAME, UAC should be disabled at all or at least run the batch
> file
> > > > with Admin privileges. It happens here sometimes too.
> > >
> > > That's very bad advice - compilers aren't security audited and shouldn't be run
> > > outside the user sandbox. The issue described is caused by windows file locking
> > > behaviour when multiple processes try to access the same file for writing in
> rapid
> > > succession. Disabling UAC or running as administrator will do nothing to fix it.
> >
> > Ok, could you please tell me what are the security issues I could encounter if I
> > compile MAME with UAC disabled (which gives me a small speedup don't ask me why and
> > less probabilities in encounter the file writing issue) at home with internet
> access
> > disabled? Are there security issues in the MSYS2 package?
>
> The code is not security audited, it could overwrite system files or registry
> registry keys or just behave badly in general. MAME also isn't security audited and
> should never be run as administrator/root. There are many potential stack smash bugs
> with potential to do more damage if running with elevated privileges.
Got it, thank you.
|
Index 
Flat 
Re: Compiling MAME
Reply
