diff options
| author | Linus Färnstrand <linus@mullvad.net> | 2019-09-30 16:52:36 +0200 |
|---|---|---|
| committer | Linus Färnstrand <linus@mullvad.net> | 2019-10-01 16:51:22 +0200 |
| commit | 10dc9392ce71dbbf9d2c7df3794c06166ee45077 (patch) | |
| tree | 9ab94153d688f61aa5c81a1595f4dd10cca24837 | |
| parent | fb9fc49131d8fd39eef169f6cd498b67b436933d (diff) | |
| download | mullvadvpn-10dc9392ce71dbbf9d2c7df3794c06166ee45077.tar.xz mullvadvpn-10dc9392ce71dbbf9d2c7df3794c06166ee45077.zip | |
Add notarizing info to README
| -rw-r--r-- | README.md | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -341,6 +341,15 @@ the version of the app you are going to release. For example `2018.3-beta1` or ` export HISTCONTROL=ignorespace export CSC_KEY_PASSWORD='my secret' ``` + * `NOTARIZE_APPLE_ID` - The AppleId to use when notarizing the app. Only needed on release builds + * `NOTARIZE_APPLE_ID_PASSWORD` - The AppleId password for the account in `NOTARIZE_APPLE_ID`. + Don't use the real AppleId password! Instead create an app specific password and add that to + your keyring. See this documentation: https://github.com/electron/electron-notarize#safety-when-using-appleidpassword + + Summary: + 1. Generate app specific password on Apple's AppleId management portal. + 2. Run `security add-generic-password -a "<apple_id>" -w <app_specific_password> -s "something_something"` + 3. Set `NOTARIZE_APPLE_ID_PASSWORD="@keychain:something_something"`. 1. Run `./build.sh` on each computer/platform where you want to create a release artifact. This will do the following for you: |