git.iko.soy/urbit.org
on master help sign in
fix other .md# links
e2c7629drbeefsupreme
content/docs/arvo/ames/ames.md+2−2
compare with master
unifiedsplit
@@ -135,7 +135,7 @@ The 32-bit header is given by the following data, presented in order:
135 - 2 bits: sender address size
135 - 2 bits: sender address size
136 - 2 bits: receiver address size
136 - 2 bits: receiver address size
137 - 20 bits: checksum (truncated insecure hash of the body, done with
137 - 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)
139 - 1 bit: is this relayed? (if set, `origin` will be present in the body)
139 - 1 bit: is this relayed? (if set, `origin` will be present in the body)
140
140
141 Every packet sent between ships is encrypted except for self-signed attestation packets from 128-bit comets.
141 Every packet sent between ships is encrypted except for self-signed attestation packets from 128-bit comets.
@@ -167,7 +167,7 @@ order:
167 filtering of honest packets sent to or from a stale life.
167 filtering of honest packets sent to or from a stale life.
168
168
169 The ciphertext is formed by `+jam`ming a `$shut-packet` and then encrypting
169 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).
171
171
172### Packeting
172### Packeting
173
173
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
37a cell with the `bone`, message number, and message fragment or ack (see
37a cell with the `bone`, message number, and message fragment or ack (see
38[Ames](/docs/arvo/ames/ames) for more information on packet structure). The
38[Ames](/docs/arvo/ames/ames) for more information on packet structure). The
39message fragment is signed using the authentication key. It is encrypted using
39message 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
41`sys/zuse.hoon`, which utilizes the 256-bit AES-SIV algorithm.
41`sys/zuse.hoon`, which utilizes the 256-bit AES-SIV algorithm.
42
42
43## Diffie-Hellman key exchange {#key-exchange}
43## Diffie-Hellman key exchange {#key-exchange}
@@ -45,7 +45,7 @@ message fragment is signed using the authentication key. It is encrypted using
45For each foreign ship a given ship has communicated with, `$ames-state` contains a
45For each foreign ship a given ship has communicated with, `$ames-state` contains a
46`$peer-state`, inside which the `$symmetric-key` (an atom which nests under
46`$peer-state`, inside which the `$symmetric-key` (an atom which nests under
47`@uw`) is utilized for encrypting all Ames packets shared between the two ships.
47`@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`,
49which is an arm utilized for generating the symmetric key for elliptic curve
49which is an arm utilized for generating the symmetric key for elliptic curve
50[Diffie-Hellman key
50[Diffie-Hellman key
51exchange](https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange)
51exchange](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
62payload is the comet's signature created with its private key. This is the only
62payload is the comet's signature created with its private key. This is the only
63circumstance under which a ship will send an unencrypted packet. The signature
63circumstance under which a ship will send an unencrypted packet. The signature
64is generated with
64is 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
66`sys/zuse.hoon`.
66`sys/zuse.hoon`.
67
67
68Upon hearing an attestation packet, the receiving ship will generate a symmetric
68Upon 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.
77## `+acru:ames` {#crypto-core}
77## `+acru:ames` {#crypto-core}
78
78
79The `+crypto-core` in `$ames-state` is an `+acru:ames` core, a
79The `+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)
81interface core for asymmetric cryptosuites found in `sys/lull.hoon` which
81interface core for asymmetric cryptosuites found in `sys/lull.hoon` which
82handles encryption, decryption, signing, and verifying. In practice, the only
82handles encryption, decryption, signing, and verifying. In practice, the only
83cryptosuite in use is [`+crub:crypto`](#crub), which implements [Suite B
83cryptosuite in use is [`+crub:crypto`](#crub), which implements [Suite B
@@ -112,7 +112,7 @@ Cryptography](https://en.wikipedia.org/wiki/NSA_Suite_B_Cryptography).
112As the `+acru` core is merely an interface, the details on how it is implemented
112As the `+acru` core is merely an interface, the details on how it is implemented
113may vary according to the cryptosuite. We summarize what each
113may vary according to the cryptosuite. We summarize what each
114core is utilized for here, but see
114core 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
116how the specific cryptosuite utilized by Ames is implemented.
116how the specific cryptosuite utilized by Ames is implemented.
117
117
118#### `+as:acru`
118#### `+as:acru`
content/docs/arvo/reference/cryptography.md+4−4
@@ -18,12 +18,12 @@ library reference.
18
18
19`zuse` contains several cryptosuites. The ones utilized by Ames are
19`zuse` contains several cryptosuites. The ones utilized by Ames are
20[`+ed:crypto`](#ed), [`+aes:crypto`](#aes), and [`+crub:crypto`](#crub), with
20[`+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.
22
22
23## `+crub:crypto` {#crub}
23## `+crub:crypto` {#crub}
24
24
25`+crub:crypto` implements an
25`+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
27[Suite B Cryptography](https://en.wikipedia.org/wiki/NSA_Suite_B_Cryptography).
27[Suite B Cryptography](https://en.wikipedia.org/wiki/NSA_Suite_B_Cryptography).
28
28
29It utilizes AES symmetric key encryption and decryption from [`+aes:crypto`](#aes)
29It 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.
203Most gates in `+ed:crypto` are [jetted](/docs/vere/jetting), meaning that an
203Most gates in `+ed:crypto` are [jetted](/docs/vere/jetting), meaning that an
204external reference library is utilized whenever these functions are called,
204external reference library is utilized whenever these functions are called,
205rather than running in Nock natively. See the [Vere
205rather 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
207library utilized by jets.
207library utilized by jets.
208
208
209## `+aes:crypto` {#aes}
209## `+aes:crypto` {#aes}
@@ -213,7 +213,7 @@ This core contains cryptographic primitives and helper functions for
213encryption and decryption. As is the case with `ed:crypto`, these
213encryption and decryption. As is the case with `ed:crypto`, these
214functionalities are utilized by [`+crub:crypto`](#crub), and most gates are
214functionalities are utilized by [`+crub:crypto`](#crub), and most gates are
215jetted. See also the Vere documentation on [AES
215jetted. 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
217utilized by jets.
217utilized by jets.
218
218
219This core contains several doors, each one used for a different variation of AES
219This 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.
20- `/lib` contains libraries that may be shared by multiple agents, threads,
20- `/lib` contains libraries that may be shared by multiple agents, threads,
21 generators, etc. However, this is not the location of the standard libraries
21 generators, etc. However, this is not the location of the standard libraries
22 (see `/sys`). Libraries are imported from `/lib` with `/+`.
22 (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.
24- `/sur` contains shared [structure](/docs/hoon/reference/rune/) definitions.
24- `/sur` contains shared [structure](/docs/hoon/reference/rune/) definitions.
25 Whenever you expect structures to be used by code across multiple files, it
25 Whenever you expect structures to be used by code across multiple files, it
26 is recommended to place their shared structures in `/sur`. Structures are
26 is recommended to place their shared structures in `/sur`. Structures are
@@ -60,7 +60,7 @@ give a brief description of each of them.
60 vanes, as well as a few functions. In particular, this includes the
60 vanes, as well as a few functions. In particular, this includes the
61 definitions of the `card`s utilized by each vane, each of which are
61 definitions of the `card`s utilized by each vane, each of which are
62 documented in their respective documentation. `lull.hoon` is loaded by the
62 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)
64 in order to prepare to create the vanes. `arvo.hoon` is the subject of `lull.hoon`.
64 in order to prepare to create the vanes. `arvo.hoon` is the subject of `lull.hoon`.
65- `zuse.hoon` is the Arvo standard library. It consists primarily of functions
65- `zuse.hoon` is the Arvo standard library. It consists primarily of functions
66 shared by the kernel and vanes, such as the ones related to
66 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.
204
204
205### `^:` ketcol
205### `^:` ketcol
206
206
207−[docs](/docs/hoon/reference/rune/ket.md#ketcol) \\,
207+[docs](/docs/hoon/reference/rune/ket#ketcol) \\,
208
208
209`[%ktcl p=spec]`: mold gate for type `p`.
209`[%ktcl p=spec]`: mold gate for type `p`.
210
210
@@ -224,7 +224,7 @@ Irregular: `` `p`q ``
224
224
225### `^*` kettar
225### `^*` kettar
226
226
227−[docs](/docs/hoon/reference/rune/ket.md#kettar) \\\*
227+[docs](/docs/hoon/reference/rune/ket#kettar) \\\*
228
228
229`[%kttr p=spec]`: produce bunt value of mold.
229`[%kttr p=spec]`: produce bunt value of mold.
230
230
content/docs/userspace/threads/http-api.md+2−2
@@ -4,7 +4,7 @@ weight = 2
4template = "doc.html"
4template = "doc.html"
5+++
5+++
6
6
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.
8
8
9Spider is bound to the `/spider` URL path, and expects the requested URL to look like:
9Spider is bound to the `/spider` URL path, and expects the requested URL to look like:
10
10
@@ -46,7 +46,7 @@ Here's an extremely simple thread that takes a `vase` of `(unit json)` and just
46(pure:m !>(json))
46(pure:m !>(json))
47```
47```
48
48
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).
50
50
51Now 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"}]`:
51Now 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"}]`:
52
52
content/grants/educational-guide-todomvc-urbit-edition.md+1−1
@@ -61,7 +61,7 @@ using it.
61
61
62This section is fairly straightforward, as it has been covered many times
62This section is fairly straightforward, as it has been covered many times
63before. ~timluc-miptev's gall guide has a [great
63before. ~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)
65of how to work with fake ships efficiently, and the existing documentation has
65of how to work with fake ships efficiently, and the existing documentation has
66plenty of material material.
66plenty of material material.
67
67