profxadke/OpenAsar
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

[Readme] Clarify Linux write protection with example command

Browse source
This commit is contained in:
Ducko 2021-12-11 10:48:13 +00:00
parent 9412a4f07d
commit dc0455eaf4
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -38,7 +38,7 @@ Custom patches are another main goal of OpenAsar, patching enhancements where ot
4. Backup your original `app.asar` (rename to `app.asar.backup` / etc) 4. Backup your original `app.asar` (rename to `app.asar.backup` / etc)
5. Install OpenAsar `app.asar` into the original path 5. Install OpenAsar `app.asar` into the original path
**If using Linux it is highly recommended to disable write protection** (needing root to overwrite files) for your Discord install if you have it enabled. It is not much of a security defecit as Windows has no write protection as well. This enables updating the asar and potentially host updating further on. **If using Linux it is highly recommended to disable write protection** (needing root to overwrite files) for your Discord install if you have it enabled. It is not much of a security defecit as Windows has no write protection as well. This enables updating the asar and potentially host updating further on. You can do this with `sudo chmod 777 <discord install path> -R`.
## Config ## Config