On 26 Jan (15:05:26), George Kadianakis wrote:
> Hey list,
Hi!
First, big thanks for this write up!
>
> with service-side prop224 implementation moving forward, we need to pin down
> the directory structure of prop224 onion services. This will be very similar to
> the current directory structure, but with some mods to facilitate assymetric
> client authorization keys and offline keys.
>
> As people have pointed out, the HS directory structure matters less after the
> introduction of ephemeral ADD_ONION onion services, but still it's an important
> part of onion service sysadmin UX.
>
> So the HiddenServiceDir directory will contain the following items:
>
> - "./hostname" [FILE]
>
> This is a file containing the onion address of the onion service.
>
> As you can see it's the same filename as in v2. Should we suffix it with v3
> to make it clear that it's v3 onion? Would we ever have v2 and v3 onions
> living in the same directory?
I don't believe we should suffix here because for almost 10 years, users/apps
have been exposed to "hostname" and it does make sense that it's the goto file
for that.
Current implementation doesn't allow two services in the same HiddenServiceDir
and for prop224, the ongoing implementation doesn't allow it either. Sharing a
directory brings all sorts of uneeded complexity. So if the directory is v3,
everything in it will be v3.
>
> - "./private_key_ed25519" [FILE]
>
> This is the file containing the private master ed25519 key of the onion service.
>
> If offline keys are _enabled_, then this file doesn't exist and instead a
> directory is made containing blinded keys for every day [TODO: The directory
> format here will be specified in the future].
If that file doesn't exists, the public key is needed else the service can't
derive the .onion and create the hostname file. The offline case is an extra
use case but I suspect we would use "public_key_ed25519" along with the
blinded keys specific file name. (Unless we make our "tor-genkey" tool
generate the hostname file as well. #bikesheding)
>
> - "./client_authorized_pubkeys" [FILE]
>
> If client authorization is _enabled_, this is a newline-separated file of
> "<client name> <pubkey>" entries for authorized clients. You can think of it
> as the ~/.ssh/authorized_keys of onion services.
>
> - "./client_authorized_privkeys/" [DIRECTORY]
> "./client_authorized_privkeys/alice" [FILE]
> "./client_authorized_privkeys/bob" [FILE]
> "./client_authorized_privkeys/charlie" [FILE]
Small clarification. The "<client name>" field in the the pubkey file is the
same for the privkey file name. So if "alice" is in the pubkey file, it will
be "alice" in this privkey directory.
>
> If client authorization is _enabled_ _AND_ if the hidden service is
> responsible for generating and distributing private keys for its clients,
> then this directory contains files with client's private keys. The idea is
> that these files can be shredded and deleted after the private key has been
> passed to the client. For more context here, please read the client
> authorization thread in [tor-dev] and see 'Appendix F' of prop224 for more
> details on how this works.
Also, expected behavior that we should go for when implementing this within
the "tor" code base. We could think of many ways to make this more complex
that it could be but going *simple* is what I'm aiming for:
- The torrc option HiddenServiceAuthorizeClient as to match the list of client
in the pubkey file in so if the pubkey file has extra entries, we error at
startup. With this in mind, here are the behaviors:
i) if a privkey file exists but no entry in the pubkey file, add the entry to
pubkey file as long as the client name is found in
HiddenServiceAuthorizeClient.
ii) a pubkey entries does NOT need a corresponding privkey to be used. As long
as the client name is found in HiddenServiceAuthorizeClient.
iii) if a client name is specified in the HiddenServiceAuthorizeClient option but
NOT in the pubkey file, generate pubkey/privkey unless the privkey file
exists which is (i) behavior where pubkey is derived from privkey.
So the great thing about this is that you can create a keypair on a different
machine (or client side), put the privkey file in the
client_authorized_privkeys directory and add the client name to torrc, HUP tor
and done. We could see ultimately an auto update of the service configuration
with the client name but I'm not a big fan of changing the torrc file
automagically...
Thanks!
David
>
> So this is it. The above should handle most uses of onion services + client
> authorization. The directory format of offline keys will be specified as we
> move forward with implementation.
>
> Hope things here are not too controversial. Looking forward to your feedback.
>
> In a few days, I will add a small Appendix section to prop224 with the
> above, and also fix the parts of 'Appendix F' that got outdated since then.
>
> Cheers!
> _______________________________________________
> tor-dev mailing list
> tor-dev@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
--
LPDGvjmCLxb+bnFoopeN77JIq714VtyU6DdFrKs4R08=
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev