4bd2316 · urbit.org · git.iko.soy

git.iko.soy/urbit.org

Fix <annotation> getting converted to HTML tag

Now-line 194 was previously only single tic surrounded and the <your whatever whatever> was getting turned into an HTML tag. Triple-tics seem to avoid this unfortunate result so surrounding it in triple-tics to resolve.

commit4bd2316a24611ff731974bb94a1ecd9118be04d7 authorrabsef-bicrym <52549148+rabsef-bicrym@users.noreply.github.com> dateFri 18 Mar 2022, 13:55 (5 years ago) parentececd99

1 file changed+5−1

compare with master

unifiedsplit

content/using/os/basics.md+5−1

content/using/os/basics.md+5−1

@@ -189,7 +189,11 @@ To add an existing moon to `jael` on a breached planet, you'll need the followin

189189 - Your moon's existing keyfile or key-string (`@uw`) _or_ the result of `pub:ex:(nol:nu:crub:crypto .^(@uv %j /=vein=/<life # of moon, per moon, here>))` _and_;

190190 - Your moon's sponsor's understanding of your moon's existing public key `pass:.^([@ud pass=@uw ~] %j /=deed=/~sampel-monler-dozzod-dozzod/<life # of moon per sponsor here>)`.

191191

192−If you only have they keyfile or key-string from your moon's last boot, you'll need to derive the `pass` value from that using `pub:ex:(nol:nu:crub:crypto key:(seed:jael:l (cue <your @uw keyfile contents or key-string contents here>)))`. This should produce a long `@ud`.

192+If you only have they keyfile or key-string from your moon's last boot, you'll need to derive the `pass` value from that using

193+```

194+pub:ex:(nol:nu:crub:crypto key:(seed:jael:l (cue <your @uw keyfile contents or key-string contents here>)))

195+```

196+This should produce a long `@ud`.

193197

194198Once you have all of the requisite elements, you can perform the following on the moon's sponsor:

195199