Skip to content

Commit cc33e3f

Browse files
committed
improve description of MATCH_PASSWORD secret
1 parent ff676a5 commit cc33e3f

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/browser/secrets.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,16 @@ You must be logged into your *GitHub* account before starting this step. If you
285285

286286
## Make up a Password
287287

288-
If you have not already made up a password, do it now and record it as <code>MATCH_PASSWORD</code>.
288+
If you have not already made up a password, do it now and record it as <code>MATCH_PASSWORD</code>. Note that if you [build more than one app](other-apps.md){: target="_blank" }, you use the same MATCH_PASSWORD for all the apps. Every app needs to have the same 6 Secrets.
289+
290+
!!! info "What is this Password used for?"
291+
The <code>MATCH_PASSWORD</code> is a **passphrase** used to encrypt and decrypt (adds security to) certificates from *Apple*.
292+
293+
A **passphrase** is similar to a password. However, a password generally refers to something used to authenticate or log into a system. A passphrase generally refers to a secret used to protect an encryption key.
294+
295+
A good passphrase should have at least 15, preferably 20 characters and be difficult to guess. It should contain upper case letters, lower case letters, digits, and preferably at least one punctuation character. No part of it should be derivable from personal information about the user or his/her family.
296+
297+
If you already created a MATCH_PASSWORD that does not meet the criteria listed above, no worries, you are protecting an *Apple* developer certificate - not the family fortune. That information is provided for new builders looking for guidance.
289298

290299
## Next Step
291300

0 commit comments

Comments
 (0)