For a couple of years, Tor has made the term hidden service
obsolete, in favor of onion service
: Tor Project | Onion Services
This PR updates all the references.
hidden service
with onion service
#19638
For a couple of years, Tor has made the term hidden service
obsolete, in favor of onion service
: Tor Project | Onion Services
This PR updates all the references.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
thx @RiccardoMasutti , for pointing this out and I somewhat like this kind of compliance on paper since disguise is the sister of hidden,
tor source code; ./src/feature/rend/rendservice.h:
0 /* Other fields */
1 crypto_pk_t *private_key; /**< Permanent hidden-service key. */
2 char service_id[REND_SERVICE_ID_LEN_BASE32+1]; /**< Onion address without
3 * '.onion' */
4 char pk_digest[DIGEST_LEN]; /**< Hash of permanent hidden-service key. */
5 smartlist_t *intro_nodes; /**< List of rend_intro_point_t's we have,
6 * or are trying to establish. */
7 /** List of rend_intro_point_t that are expiring. They are removed once
8 * the new descriptor is successfully uploaded. A node in this list CAN
9 * NOT appear in the intro_nodes list. */
names it, what it should be ?
So imho facts become not that different by wording. But as this is kind of compliance on paper and disguise the sister of hidden, I somewhat like it.
The moment even
HiddenServiceDir
parameter for use in torrc get renamed we should act.
1437@@ -1438,7 +1438,7 @@
1438 </message>
688@@ -689,7 +689,7 @@ and git merge commit are mentioned.
689 - #8567 `85d4e21` Add default port numbers to REST doc (djpnewton)
Concept ACK. I think ‘onion service’ describes more concretely than ‘hidden service’ what is being talked about.
it looks like this PR is a drive-by search and replace that touches a number of files that are auto-generated or not usually changed.
Yes.
And please squash this into one commit when done.
192@@ -193,7 +193,7 @@ Accept connections from outside (default: 1 if no \fB\-proxy\fR or \fB\-connect\
193 .HP
194 \fB\-listenonion\fR
195 .IP
196-Automatically create Tor hidden service (default: 1)
197+Automatically create Tor onion service (default: 1)
man
files states: DO NOT MODIFY THIS FILE! It was generated by...
Concept ACK assuming @laanwj’s feedback is addressed
Welcome as a contributor @RiccardoMasutti! :)
You need to squash your changes into a single commit, and use a proper commit message. i.e:
0doc: replace hidden service with onion service
1
2For a couple of years, Tor documentation has made
3the term hidden service obsolete, in favor of onion
4service.
5
6This PR updates all the references in the code base.
109@@ -110,7 +110,7 @@ Connecting to Tor's control socket API requires one of two authentication method
110 configured. It also requires the control socket to be enabled, e.g. put `ControlPort 9051`
111 in `torrc` config file. For cookie authentication the user running bitcoind must have read
112 access to the `CookieAuthFile` specified in Tor configuration. In some cases this is
113-preconfigured and the creation of a hidden service is automatic. If permission problems
114+preconfigured and the creation of a onion service is automatic. If permission problems
Welcome as a contributor @RiccardoMasutti! :)
Yes and thanks for sticking with this, most admit that it’s not really documented anywhere which files you are and are not allowed to change.
For a couple of years, Tor documentation has made
the term hidden service obsolete, in favor of onion
service.
This PR updates all the references in the code base.
ACK 1e72b68ab330c72644981508c8a1b3fa670d086f, tested on Linux Mint 20 (x86_64).
The GUI-related changes: