aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md11
1 files changed, 0 insertions, 11 deletions
diff --git a/README.md b/README.md
index 1bc1f5e1f..87006e667 100644
--- a/README.md
+++ b/README.md
@@ -54,17 +54,6 @@ Assets made available via [GitHub releases](https://github.com/ferdium/ferdium-a
54 54
55_Find answers to frequently asked questions on [ferdium.org/faq](https://ferdium.org/faq)._ 55_Find answers to frequently asked questions on [ferdium.org/faq](https://ferdium.org/faq)._
56 56
57## Unsigned Nightlies on MacOS
58
59Since we are waiting to acquire the Apple Developer License, we are publishing our nightlies without being signed. On MacOS Catalina and newer, you will receive the prompt that "Ferdium" cannot be opened because the developer cannot be verified.
60
61To work around this, simply Control/Right-click on the app and select "Open" twice.
62
63Alternatively, click "Open Anyway" under the "General" section of Security & Privacy of the "System Preferences" application, or execute the following command:
64```bash
65sudo xattr -rd com.apple.quarantine /Applications/Ferdium.app
66```
67
68## Unsigned Nightlies on Windows 57## Unsigned Nightlies on Windows
69 58
70Similarly to the MacOS, we do not currently have a certificate to sign the nightlies on Windows. For this reason, an error will appear when launching the setup tool or the portable app if your execution policy is not set to `Bypass` or `Unrestricted`. In order to allow the script to run, it is sufficient to right-click on the `.exe` to access its properties and to tick the box labeled `Unblock` at the bottom of the General tab. Alternatively, you could execute the following in a PowerShell: 59Similarly to the MacOS, we do not currently have a certificate to sign the nightlies on Windows. For this reason, an error will appear when launching the setup tool or the portable app if your execution policy is not set to `Bypass` or `Unrestricted`. In order to allow the script to run, it is sufficient to right-click on the `.exe` to access its properties and to tick the box labeled `Unblock` at the bottom of the General tab. Alternatively, you could execute the following in a PowerShell: