| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It was never implemented, is not specified, and neither dgoulet nor
I can quite remember how it was supposed to work.
|
|
By our current logic, it needs to have `hs` in it.
|
|
It has no independent existence outside of the encryption algorithm
of 2.5.3.
|
|
|
|
These names are slightly shorter and a bit more descriptive IMO, and
now (when they are still fresh) is the best time to rename these
keys.
`hs_intro_tid` becomes `hs_ipt_sid`: It is a _session identifier_
key used with an _introduction point_. Using `ipt` here emphasizes
that it is not part of the introduction _handshake_.
`hs_intro_ntor` becomes `hss_ntor`. The extra "s" means it is owned
by the service. Renaming "intro" here removes the implication that
it is held by or used by the introduction point.
`onion_ntor` becomes `ntor`: There is no such thing as an ntor key
that is not an onion key.
|
|
(See text for more info!)
|
|
The spec says "exactly once", but that only refers to the ntor
variant.
|
|
|
|
It looks like C tor doesn't include a final newline in the middle
layer of its onion service descriptors. That made arti reject them
the first time I tried to parse one! Here I document this behavior,
and tell other implementations what to do.
|
|
Based on this email thread with dgoulet:
https://lists.torproject.org/pipermail/tor-dev/2023-January/014808.html
|
|
As per review comments
|
|
|
|
|
|
This reverts commit 81c1be641557d1cd3fb6d9195de08e9f411be517.
|
|
|
|
|
|
Prompted by
https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/105#note_2869614
|
|
Suggested here
https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/105#note_2869613
|
|
Even the ones that are actually ntor. Perhaps that's wrong and those
should be ntor? Personally I like it this way.
|
|
In particular, give these formal names which contain "hs" (since they
are part of the hidden service protocol, and not any other kind of
authentication or authorisation scheme), and "N" to indicate that they
are hash-generated nonces, not passwords.
Change the references in the formulae, which it really seems to me
ought to refer to the formal names.
|
|
|
|
Introduce the credential and subcredential before we use them.
Talk about the public identity key rather than the credential,
when we can.
|
|
|
|
|
|
All supported versions for relays on the Tor network support v3
onion services. As such, we can mark the sections about "how do I
use an 0.2.9.x relay as my intro/rend point?" as obsolete.
|
|
|
|
|
|
These patch changes describe new default behaviors for extension
field lists, as appear in ntor3 and in many places throughout the
ntor3 protocol. In general:
* Unrecognized extensions MUST be ignored.
Additionally, all the following rules apply _unless otherwise stated
in the documentation for an extension.
* Extensions are sent in sorted order.
* Extensions should only be sent once in a message
* If you receive multiple copies of an extension, only the first
one counts.
This comes out of discussions on tor!525.
|
|
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
- "auth-client" is actually a mandatory field right now.
- The intro point cross-certificates are the other way around (#29853)
- The descriptor MAC includes the salt_len and it's not the
standard v3 MAC format.
|
|
This only adds newline characters to make the existing text blocks act like
"blockquote" or "code block" syntax in Markdown, asciidoc, and others.
This was accomplished by manually reviewing the output of this script:
```bash
for f in *.txt; do
cat $f | python -c "import sys,re;print(re.sub(r'(\n {0,3}[^ \n][^\n]*\n)( {4,}[^\n]*)', r'\1\n\2', sys.stdin.read()))" > ${f}.tmp
mv ${f}.tmp $f
done
```
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
This is one small step towards making these a standard, parsable format.
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Spec for #23588.
|
|
Spec for 23507 and 23818.
|
|
|
|
|
|
Pointed out by Jean Chevalier.
|
|
|
|
- Add file extension to the client auth files.
- Better specify suggested client auth file format.
- Suggest better client auth logic for client and service side.
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
|
|
|
