diff options
author | André Oliveira <37463445+SpecialAro@users.noreply.github.com> | 2022-06-22 02:18:26 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-06-22 01:18:26 +0000 |
commit | b1a75ddf0533eb04d4d066a38f45567c3c526a6b (patch) | |
tree | 3c324cec6092cde48fed8eec78d7532355072f34 /README.md | |
parent | Comment flair-id to see if it is the cause of failing (diff) | |
download | ferdium-app-b1a75ddf0533eb04d4d066a38f45567c3c526a6b.tar.gz ferdium-app-b1a75ddf0533eb04d4d066a38f45567c3c526a6b.tar.zst ferdium-app-b1a75ddf0533eb04d4d066a38f45567c3c526a6b.zip |
Remove Unsigned nightlies on macOS on README [skip ci] (#334)
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 11 |
1 files changed, 0 insertions, 11 deletions
@@ -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 | |||
59 | Since 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 | |||
61 | To work around this, simply Control/Right-click on the app and select "Open" twice. | ||
62 | |||
63 | Alternatively, click "Open Anyway" under the "General" section of Security & Privacy of the "System Preferences" application, or execute the following command: | ||
64 | ```bash | ||
65 | sudo xattr -rd com.apple.quarantine /Applications/Ferdium.app | ||
66 | ``` | ||
67 | |||
68 | ## Unsigned Nightlies on Windows | 57 | ## Unsigned Nightlies on Windows |
69 | 58 | ||
70 | Similarly 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: | 59 | Similarly 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: |