diff options
| author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2024-03-05 11:49:02 +0000 |
|---|---|---|
| committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2024-03-05 15:42:53 +0000 |
| commit | 9fedec9a1ebbb18d08334d7edf0e17b0a458b6fd (patch) | |
| tree | 2740217590ba745f99baf5805f51b8afd7407fe8 /spec/rend-spec/hsdesc-encrypt.md | |
| parent | 81942fbbc418d1fadbb8f84c10d46ccc74e52c58 (diff) | |
| download | torspec-9fedec9a1ebbb18d08334d7edf0e17b0a458b6fd.tar.gz torspec-9fedec9a1ebbb18d08334d7edf0e17b0a458b6fd.zip | |
hspow: Use consistent terminology for hspow schemes
The text uses "scheme" and "version" a couple of times. The formal
protocol says "type". The terminology should be consistent. IMO
"scheme" is the best word to use. "version" is particularly bad.
Change all references to "type" and "version" to "scheme".
Diffstat (limited to 'spec/rend-spec/hsdesc-encrypt.md')
| -rw-r--r-- | spec/rend-spec/hsdesc-encrypt.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/spec/rend-spec/hsdesc-encrypt.md b/spec/rend-spec/hsdesc-encrypt.md index 3e91172..86abfae 100644 --- a/spec/rend-spec/hsdesc-encrypt.md +++ b/spec/rend-spec/hsdesc-encrypt.md @@ -252,21 +252,21 @@ list of intro points etc. The plaintext has the following format: ``` ```text - "pow-params" SP type SP seed-b64 SP suggested-effort + "pow-params" SP scheme SP seed-b64 SP suggested-effort SP expiration-time NL - [At most once per "type"] + [At most once per "scheme"] If present, this line provides parameters for an optional proof-of-work client puzzle. A client that supports an offered scheme can include a corresponding solution in its introduction request to improve priority in the service's processing queue. - Only version 1 is currently defined. - Other versions may have a different format. + Only scheme `v1` is currently defined. + Other schemes may have a different format. Introduced in tor-0.4.8.1-alpha. - type: The type of PoW system used. We call the one specified here "v1". + scheme: The PoW system used. We call the one specified here "v1". seed-b64: A random seed that should be used as the input to the PoW hash function. Should be 32 random bytes encoded in base64 |