Northstar
Northstar copied to clipboard
R2Northstar
Deal with EA App complications
~~EA App sets a read-only lock (todo double check) on game folders such as Titanfall2 which causes issues both for mod-managers and Northstar trying to access it.~~
Having Titanfall2 installed in C:\Program Files\EA Games\Titanfall2 makes it unable for other applications to write to that directory such as Northstar.
One solution is simply to run the relevant application as admin, however, that is a huge security risk as for example if there exists an exploit that allows an attacker to compromise the Northstar client, they immediately gain admin rights.
As such we need to find a solution that is both easy to execute by the user (preferably they don't need to do anything and we just handle it in client/mod-manager) and does not introduce any new security risks.
Note that simply removing the read-only look does not seem to work as it appears to be reset by EA app using some background service (todo, double-check/confirm).
One solution is simply to run the relevant application as admin, however, that is a huge security risk as for example if there exists an exploit that allows an attacker to compromise the Northstar client, they immediately gain admin rights.
Instead of launching Northstar as admin, you could create a very simple executable that only does one thing: remove the read-only flag. Northstar and other applications could launch this tool before anything else and don't have to worry about it. In terms of security, this would be a better solution than running Nothing or Mod Managers as admin and since the tool would only do one thing, it is easier to secure.
As for the users, they would be greeted with a UAC dialog every time they start the game or Mod Manager.
remove the read-only flag. Northstar and other applications could launch this tool before anything else and don't have to worry about it
Based on a user that has EA App, they removed the read-only lock via the Windows folder property view and upon opening property view again, it was back. So I have doubts, that that's enough... :/
We'd need more information when and how EA Desktop updates the file attributes. I doubt they listen for changes or do it on an interval, it's likely during startup of something.
Also does this only happen for Titanfall 2 installed via EA Desktop or also with Steam?
I have Origin based Titanfall2 build and I'm getting this read-only lock. I never once used Steam to install the game or EA Desktop.
It seems EA App complications are only caused when the game is installed to C:\Program Files\EA Games\, meaning that the issue is not caused by EA App but rather a consequence of being located in a protected directory Program Files. Origin and Steam do not face this issue as they use Program Files (x86) which to my knowledge has no admin protections or the like for legacy support.
The best solution for EA App therefore seems to be to move the game install to a different location, see also https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#cannot-write-log-file-when-using-northstar-on-ea-app
I have a riddle for you @GeckoEidechse .
I have the Read-Only lock problem, inside of a custom installation directory.
See below:
Might not even be Titanfall 2 related for me though as I'm realizing all? of my folders have read-only locks on them.
How having read-only lock on the custom installation directory or having read-only locks on all my folders?