0ae40db7b6d39a098c5c5f3312175d6d3d3c211f
howto/Registry-Authentication.md
| ... | ... | @@ -78,18 +78,18 @@ If you lose access to all existing keys, you can recover your `mntner` object us |
| 78 | 78 | |
| 79 | 79 | **Note: Key recovery is a fallback mechanism** You should look to review and improve your key backup process after completing this procedure. |
| 80 | 80 | |
| 81 | -1) Ensure the email address listed in your `person` object is added to your Gitea account and is verified. |
|
| 82 | -2) Update your `mntner` object with your new public key(s). |
|
| 83 | -3) Sign the commit using one of the **new** keys. |
|
| 84 | -4) Push your branch and open a PR. |
|
| 85 | -5) Post a comment on the PR with the exact text: |
|
| 81 | +1. Ensure the email address listed in your `person` object is added to your Gitea account and is verified. |
|
| 82 | +2. Update your `mntner` object with your new public key(s). |
|
| 83 | +3. Sign the commit using one of the **new** keys. |
|
| 84 | +4. Push your branch and open a PR. |
|
| 85 | +5. Post a comment on the PR with the exact text: |
|
| 86 | 86 | |
| 87 | 87 | ``` text |
| 88 | 88 | ### DN42 Recovery |
| 89 | 89 | ``` |
| 90 | 90 | |
| 91 | -6) In the Gitea UI, request a re-review from the *pipeline* user to re-run the check. |
|
| 92 | -7) The *pipeline* will authorise the change if your verified Gitea email address matches an email in your `person` object. |
|
| 91 | +6. In the Gitea UI, request a re-review from the *pipeline* user to re-run the check. |
|
| 92 | +7. The *pipeline* will authorise the change if your verified Gitea email address matches an email in your `person` object. |
|
| 93 | 93 | |
| 94 | 94 | --- |
| 95 | 95 |