git.iko.soy/urbit.org
on master help sign in
fix other .md# links
commite2c762922f662cf564370fa45673c3d13f71f693 authordrbeefsupreme <drbeefsupreme@discordja.net> dateWed 4 Aug 2021, 13:26 (5 years ago) parentd8fe406
7 files changed+18−18
compare with master
unifiedsplit
content/docs/arvo/ames/ames.md+2−2 content/docs/arvo/ames/cryptography.md+5−5 content/docs/arvo/reference/cryptography.md+4−4 content/docs/arvo/reference/filesystem.md+2−2 content/docs/hoon/reference/irregular.md+2−2 content/docs/userspace/threads/http-api.md+2−2 content/grants/educational-guide-todomvc-urbit-edition.md+1−1
content/docs/arvo/ames/ames.md+2−2
@@ -135,7 +135,7 @@ The 32-bit header is given by the following data, presented in order:
135135 - 2 bits: sender address size
136136 - 2 bits: receiver address size
137137 - 20 bits: checksum (truncated insecure hash of the body, done with
138− [`+mug`](/docs/hoon/reference/stdlib/2e.md#mug)
138+ [`+mug`](/docs/hoon/reference/stdlib/2e#mug)
139139 - 1 bit: is this relayed? (if set, `origin` will be present in the body)
140140
141141 Every packet sent between ships is encrypted except for self-signed attestation packets from 128-bit comets.
@@ -167,7 +167,7 @@ order:
167167 filtering of honest packets sent to or from a stale life.
168168
169169 The ciphertext is formed by `+jam`ming a `$shut-packet` and then encrypting
170− using [`+en:sivc:aes:crypto`](/docs/arvo/reference/cryptography.md#en).
170+ using [`+en:sivc:aes:crypto`](/docs/arvo/reference/cryptography#en).
171171
172172### Packeting
173173
content/docs/arvo/ames/cryptography.md+5−5
@@ -37,7 +37,7 @@ The encrypted payload of each packet is a `$shut-packet`, which is the `+jam` of
3737a cell with the `bone`, message number, and message fragment or ack (see
3838[Ames](/docs/arvo/ames/ames) for more information on packet structure). The
3939message fragment is signed using the authentication key. It is encrypted using
40−[`+en:crub:crypto`](/docs/arvo/reference/cryptography.md#en) found in
40+[`+en:crub:crypto`](/docs/arvo/reference/cryptography#en) found in
4141`sys/zuse.hoon`, which utilizes the 256-bit AES-SIV algorithm.
4242
4343## Diffie-Hellman key exchange {#key-exchange}
@@ -45,7 +45,7 @@ message fragment is signed using the authentication key. It is encrypted using
4545For each foreign ship a given ship has communicated with, `$ames-state` contains a
4646`$peer-state`, inside which the `$symmetric-key` (an atom which nests under
4747`@uw`) is utilized for encrypting all Ames packets shared between the two ships.
48−The `symmetric-key` is derived using [`+shar:ed:crypto`](/docs/arvo/reference/cryptography.md#ed) found in `sys/zuse.hoon`,
48+The `symmetric-key` is derived using [`+shar:ed:crypto`](/docs/arvo/reference/cryptography#ed) found in `sys/zuse.hoon`,
4949which is an arm utilized for generating the symmetric key for elliptic curve
5050[Diffie-Hellman key
5151exchange](https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange)
@@ -62,7 +62,7 @@ its identity with an "attestation packet". This is an unencrypted packet whose
6262payload is the comet's signature created with its private key. This is the only
6363circumstance under which a ship will send an unencrypted packet. The signature
6464is generated with
65−[`+sign:as:crub`](/docs/arvo/reference/cryptography.md#sign-as) found in
65+[`+sign:as:crub`](/docs/arvo/reference/cryptography#sign-as) found in
6666`sys/zuse.hoon`.
6767
6868Upon hearing an attestation packet, the receiving ship will generate a symmetric
@@ -77,7 +77,7 @@ with a non-comet. This is a technical limitation with a planned workaround.
7777## `+acru:ames` {#crypto-core}
7878
7979The `+crypto-core` in `$ames-state` is an `+acru:ames` core, a
80−[lead](/docs/hoon/reference/advanced.md#dry-polymorphism-and-core-nesting-rules)
80+[lead](/docs/hoon/reference/advanced#dry-polymorphism-and-core-nesting-rules)
8181interface core for asymmetric cryptosuites found in `sys/lull.hoon` which
8282handles encryption, decryption, signing, and verifying. In practice, the only
8383cryptosuite in use is [`+crub:crypto`](#crub), which implements [Suite B
@@ -112,7 +112,7 @@ Cryptography](https://en.wikipedia.org/wiki/NSA_Suite_B_Cryptography).
112112As the `+acru` core is merely an interface, the details on how it is implemented
113113may vary according to the cryptosuite. We summarize what each
114114core is utilized for here, but see
115−[`crub:crypto`](/docs/arvo/reference/cryptography.md#crub) for more details on
115+[`crub:crypto`](/docs/arvo/reference/cryptography#crub) for more details on
116116how the specific cryptosuite utilized by Ames is implemented.
117117
118118#### `+as:acru`
content/docs/arvo/reference/cryptography.md+4−4
@@ -18,12 +18,12 @@ library reference.
1818
1919`zuse` contains several cryptosuites. The ones utilized by Ames are
2020[`+ed:crypto`](#ed), [`+aes:crypto`](#aes), and [`+crub:crypto`](#crub), with
21−the latter being the only one which is implemented as an [`+acru:ames`](/docs/arvo/ames/cryptography.md#crypto-core)-shaped core.
21+the latter being the only one which is implemented as an [`+acru:ames`](/docs/arvo/ames/cryptography#crypto-core)-shaped core.
2222
2323## `+crub:crypto` {#crub}
2424
2525`+crub:crypto` implements an
26−[`+acru:ames`](/docs/arvo/ames/cryptography.md#crypto-core) core that implements
26+[`+acru:ames`](/docs/arvo/ames/cryptography#crypto-core) core that implements
2727[Suite B Cryptography](https://en.wikipedia.org/wiki/NSA_Suite_B_Cryptography).
2828
2929It utilizes AES symmetric key encryption and decryption from [`+aes:crypto`](#aes)
@@ -203,7 +203,7 @@ only cryptosuite which [Ames](/docs/arvo/ames/ames) makes use of.
203203Most gates in `+ed:crypto` are [jetted](/docs/vere/jetting), meaning that an
204204external reference library is utilized whenever these functions are called,
205205rather than running in Nock natively. See the [Vere
206−documentation](/docs/vere/cryptography.md#ed) for more information about the
206+documentation](/docs/vere/cryptography#ed) for more information about the
207207library utilized by jets.
208208
209209## `+aes:crypto` {#aes}
@@ -213,7 +213,7 @@ This core contains cryptographic primitives and helper functions for
213213encryption and decryption. As is the case with `ed:crypto`, these
214214functionalities are utilized by [`+crub:crypto`](#crub), and most gates are
215215jetted. See also the Vere documentation on [AES
216−SIV](/docs/vere/cryptography.md#aes) for more information about the library
216+SIV](/docs/vere/cryptography#aes) for more information about the library
217217utilized by jets.
218218
219219This core contains several doors, each one used for a different variation of AES
content/docs/arvo/reference/filesystem.md+2−2
@@ -20,7 +20,7 @@ definitions in `/lib`, for example.
2020- `/lib` contains libraries that may be shared by multiple agents, threads,
2121 generators, etc. However, this is not the location of the standard libraries
2222 (see `/sys`). Libraries are imported from `/lib` with `/+`.
23−- `/mar` contains [mark](/docs/arvo/clay/architecture.md#marks) definitions.
23+- `/mar` contains [mark](/docs/arvo/clay/architecture#marks) definitions.
2424- `/sur` contains shared [structure](/docs/hoon/reference/rune/) definitions.
2525 Whenever you expect structures to be used by code across multiple files, it
2626 is recommended to place their shared structures in `/sur`. Structures are
@@ -60,7 +60,7 @@ give a brief description of each of them.
6060 vanes, as well as a few functions. In particular, this includes the
6161 definitions of the `card`s utilized by each vane, each of which are
6262 documented in their respective documentation. `lull.hoon` is loaded by the
63− kernel during the [larval stage](/docs/arvo/overview.md#larval-stage-core)
63+ kernel during the [larval stage](/docs/arvo/overview#larval-stage-core)
6464 in order to prepare to create the vanes. `arvo.hoon` is the subject of `lull.hoon`.
6565- `zuse.hoon` is the Arvo standard library. It consists primarily of functions
6666 shared by the kernel and vanes, such as the ones related to
content/docs/hoon/reference/irregular.md+2−2
@@ -204,7 +204,7 @@ Lets us adjust types without violating type constraints.
204204
205205### `^:` ketcol
206206
207−[docs](/docs/hoon/reference/rune/ket.md#ketcol) \\,
207+[docs](/docs/hoon/reference/rune/ket#ketcol) \\,
208208
209209`[%ktcl p=spec]`: mold gate for type `p`.
210210
@@ -224,7 +224,7 @@ Irregular: `` `p`q ``
224224
225225### `^*` kettar
226226
227−[docs](/docs/hoon/reference/rune/ket.md#kettar) \\\*
227+[docs](/docs/hoon/reference/rune/ket#kettar) \\\*
228228
229229`[%kttr p=spec]`: produce bunt value of mold.
230230
content/docs/userspace/threads/http-api.md+2−2
@@ -4,7 +4,7 @@ weight = 2
44template = "doc.html"
55+++
66
7−Spider has an Eyre binding which allows threads to be run externally via [authenticated](/docs/arvo/eyre/external-api-ref.md#authentication) HTTP POST requests.
7+Spider has an Eyre binding which allows threads to be run externally via [authenticated](/docs/arvo/eyre/external-api-ref#authentication) HTTP POST requests.
88
99Spider is bound to the `/spider` URL path, and expects the requested URL to look like:
1010
@@ -46,7 +46,7 @@ Here's an extremely simple thread that takes a `vase` of `(unit json)` and just
4646(pure:m !>(json))
4747```
4848
49−First we must obtain a session cookie by [authenticating](/docs/arvo/eyre/examples.md#authenticating).
49+First we must obtain a session cookie by [authenticating](/docs/arvo/eyre/examples#authenticating).
5050
5151Now we can try and run our thread. Spider is bound to the `/spider` URL path, and expects the rest of the path to be `/{inputMark}/{thread}/{outputMark}`. Our `{thread}` is called `eyre-thread`, and both its `{inputMark}` and `{outputMark}` are `json`, so our URL path will be `/spider/json/eyre-agent/json`. Our request will be an HTTP POST request and the body will be some `json`, in this case `[{"foo": "bar"}]`:
5252
content/grants/educational-guide-todomvc-urbit-edition.md+1−1
@@ -61,7 +61,7 @@ using it.
6161
6262This section is fairly straightforward, as it has been covered many times
6363before. ~timluc-miptev's gall guide has a [great
64−overview](https://github.com/timlucmiptev/gall-guide/blob/master/workflow.md#three-workflow-options)
64+overview](https://github.com/timlucmiptev/gall-guide/blob/master/workflow#three-workflow-options)
6565of how to work with fake ships efficiently, and the existing documentation has
6666plenty of material material.
6767