[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor/maint-0.3.5] man: Document HSv3 client authorization revocation
commit 0906dde9d5ac409caf9f70ea7ec00efc42ec27ca
Author: David Goulet <dgoulet@xxxxxxxxxxxxxx>
Date: Mon Dec 3 11:22:14 2018 -0500
man: Document HSv3 client authorization revocation
Removing a ".auth" file revokes a client access to the service but the
rendezvous circuit is not closed service side because the service simply
doesn't know which circuit is for which client.
This commit notes in the man page that to fully revoke a client access to the
service, the tor process should be restarted.
Closes #28275
Signed-off-by: David Goulet <dgoulet@xxxxxxxxxxxxxx>
---
changes/ticket28275 | 4 ++++
doc/tor.1.txt | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/changes/ticket28275 b/changes/ticket28275
new file mode 100644
index 000000000..eadca86b7
--- /dev/null
+++ b/changes/ticket28275
@@ -0,0 +1,4 @@
+ o Documentation (hidden service v3, man page):
+ - Note in the man page that the only real way to fully revoke an onion
+ service v3 client authorization is by restarting the tor process. Closes
+ ticket 28275.
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index 097db065b..581783dd6 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -2961,6 +2961,10 @@ Note that once you've configured client authorization, anyone else with the
address won't be able to access it from this point on. If no authorization is
configured, the service will be accessible to anyone with the onion address.
+Revoking a client can be done by removing their ".auth" file, however the
+revocation will be in effect only after the tor process gets restarted even if
+a SIGHUP takes place.
+
See the Appendix G in the rend-spec-v3.txt file of
https://spec.torproject.org/[torspec] for more information.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits