Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

datashards: Update from 0p to p0 #172

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

datashards: Update from 0p to p0 #172

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions topics-and-advance-readings/datashards-rationale.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,13 +161,13 @@ Immutable content is represented by the following URI convention:

Here is an example IDSC URI:

idsc:0p.X74UbU3NoLTA_Nupi8DhaJ_oQpQ95KFukMAkJJotKgo.eekxqfiZIcEnc8cpR-sD_3X3qLaTzQW-KnovArMkGP0
idsc:p0.X74UbU3NoLTA_Nupi8DhaJ_oQpQ95KFukMAkJJotKgo.eekxqfiZIcEnc8cpR-sD_3X3qLaTzQW-KnovArMkGP0

The components of such a URI can be broken down as follows:

- **suite-id**: A string of characters representing the "suite" of
encryption protocols used by this IDSC.
In the above example, the value is `0p`, for the prototype 0th
In the above example, the value is `p0`, for the prototype 0th
suite, which uses [sha256d](https://en.bitcoinwiki.org/wiki/SHA-256d) hashes (double application of sha256
to prevent [length extension attacks](https://en.wikipedia.org/wiki/Length_extension_attack)) for content and `aes-ctr` for
encryption.
Expand Down Expand Up @@ -263,9 +263,9 @@ The components of MDSC URIs are:
for read-write-verify.
- **suite-id**: A string of characters representing the "suite" of
encryption protocols used by this IDSC. In the above examples, the
value is `0p`, for the prototype 0th suite, which uses a
value is `p0`, for the prototype 0th suite, which uses a
combination of RSA public/private keypairs for the verify/write
keys, the `0p` IDSC suite for looking up the verification key, and
keys, the `p0` IDSC suite for looking up the verification key, and
`sha256` to convert a write key to a read key.
- **keydata-hash** and **keydata-enckey**: Used to look up the
keydata for this MDSC object, which when retrieved contains
Expand All @@ -289,15 +289,15 @@ The components of MDSC URIs are:
Some examples of MDSC capability URIs:

# verify ocap
mdsc:v.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g
mdsc:v.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g
# verify-read ocap
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs
# verify-read ocap for revision 1
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/
# verify-read ocap for revision 1, specific hash
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/bNIYWl3VtH5e3m0Znp80fU5qtH6IvqpGl3GlyXmNoD0
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/bNIYWl3VtH5e3m0Znp80fU5qtH6IvqpGl3GlyXmNoD0
# verify-read-write ocap
mdsc:w.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.MeMgmy_j0CI8jwT0EUX01bF7N0UAVSYwHhNQ67h2WAE
mdsc:w.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.MeMgmy_j0CI8jwT0EUX01bF7N0UAVSYwHhNQ67h2WAE

As stated before, there is no guarantee that multiple conflicting
revisions won't be issued, or that a user requesting the latest
Expand Down
18 changes: 9 additions & 9 deletions topics-and-advance-readings/datashards-rationale.org
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,13 +157,13 @@ Immutable content is represented by the following URI convention:

Here is an example IDSC URI:

: idsc:0p.X74UbU3NoLTA_Nupi8DhaJ_oQpQ95KFukMAkJJotKgo.eekxqfiZIcEnc8cpR-sD_3X3qLaTzQW-KnovArMkGP0
: idsc:p0.X74UbU3NoLTA_Nupi8DhaJ_oQpQ95KFukMAkJJotKgo.eekxqfiZIcEnc8cpR-sD_3X3qLaTzQW-KnovArMkGP0

The components of such a URI can be broken down as follows:

- *suite-id*: A string of characters representing the "suite" of
encryption protocols used by this IDSC.
In the above example, the value is =0p=, for the prototype 0th
In the above example, the value is =p0=, for the prototype 0th
suite, which uses [[https://en.bitcoinwiki.org/wiki/SHA-256d][sha256d]] hashes (double application of sha256
to prevent [[https://en.wikipedia.org/wiki/Length_extension_attack][length extension attacks]]) for content and =aes-ctr= for
encryption.
Expand Down Expand Up @@ -256,9 +256,9 @@ The components of MDSC URIs are:
for read-write-verify.
- *suite-id*: A string of characters representing the "suite" of
encryption protocols used by this IDSC. In the above examples, the
value is =0p=, for the prototype 0th suite, which uses a
value is =p0=, for the prototype 0th suite, which uses a
combination of RSA public/private keypairs for the verify/write
keys, the =0p= IDSC suite for looking up the verification key, and
keys, the =p0= IDSC suite for looking up the verification key, and
=sha256= to convert a write key to a read key.
- *keydata-hash* and *keydata-enckey*: Used to look up the
keydata for this MDSC object, which when retrieved contains
Expand All @@ -283,15 +283,15 @@ Some examples of MDSC capability URIs:

#+BEGIN_SRC text
# verify ocap
mdsc:v.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g
mdsc:v.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g
# verify-read ocap
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs
# verify-read ocap for revision 1
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/
# verify-read ocap for revision 1, specific hash
mdsc:r.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/bNIYWl3VtH5e3m0Znp80fU5qtH6IvqpGl3GlyXmNoD0
mdsc:r.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.wtNehlhYRxooG1un7cLBDMvjs2S-uEz1jLFgfDEH3Cs/1/bNIYWl3VtH5e3m0Znp80fU5qtH6IvqpGl3GlyXmNoD0
# verify-read-write ocap
mdsc:w.0p.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.MeMgmy_j0CI8jwT0EUX01bF7N0UAVSYwHhNQ67h2WAE
mdsc:w.p0.gl6qBg6i3dc5dz9cylxPcxIWn4SgLdTxWFzyqtwIljk.6B4Vy69Z6GnqF3VAk8eZkUBZbXgR5tWWoC1C_6Pbe7g.MeMgmy_j0CI8jwT0EUX01bF7N0UAVSYwHhNQ67h2WAE
#+END_SRC

As stated before, there is no guarantee that multiple conflicting
Expand Down