torproject/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-12-06 19:41:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

0.3.5 changelog cleanups

Browse Source
This commit is contained in:
Roger Dingledine
2021-10-25 12:06:40 -04:00
parent 5aa7bd4308
commit 08e4b8d2fc
2 changed files with 36 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ChangeLog
+18 -18
View File
@@ -1,22 +1,22 @@
Changes in version 0.3.5.17 - 2021-10-26
This version as a major change which is that v2 onion service are now
disabled at the client, service and relay meaning that any tor nodes
running this version and onward will stops supporting v2. This is the
last step into the long deprecation process of onion service version
2. Everyone running an earlier version, whether as a client, a relay,
or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or
0.4.6.8.
The major change in this version is that v2 onion services are now
disabled at the client, service, and relay: any Tor nodes running this
version and onward will stop supporting v2 onion services. This is the
last step in the long deprecation process of v2 onion services.
Everyone running an earlier version, whether as a client, a relay, or
an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
or 0.4.6.8.
o Major feature (onion service v2, backport from 0.4.5.11):
- See https://blog.torproject.org/v2-deprecation-timeline for
details on how to transition from v2 to v3.
- The control port command HSFETCH and HSPOST don't allow version 2
as well. It is also not possible to create a v2 service with
ADD_ONION.
- Tor does NOT allow anymore to create v2 services, to connect as a
client to a v2 service and for a relay to be a v2 HSDir or
introduction point. This effectively disable onion service version
2 tor wide. Closes 40476.
- The control port commands HSFETCH and HSPOST no longer allow
version 2, and it is no longer possible to create a v2 service
with ADD_ONION.
- Tor no longer allows creating v2 services, or connecting as a
client to a v2 service. Relays will decline to be a v2 HSDir or
introduction point. This effectively disables onion service
version 2 Tor-wide. Closes ticket 40476.
o Minor features (bridge, backport from 0.4.6.8):
- We now announce the URL to Tor's new bridge status at
@@ -24,15 +24,15 @@ Changes in version 0.3.5.17 - 2021-10-26
bridge relay. Closes ticket 30477.
o Minor features (fallbackdir):
- Regenerate fallback directories for October 2021. Close
- Regenerate fallback directories for October 2021. Closes
ticket 40493.
o Minor bugfixes (compatibility, backport from 0.4.6.8):
- Fix compatibility with the most recent Libevent versions, which no
longer have an evdns_set_random_bytes() function. Because this
longer have an evdns_set_random_bytes() function. Because this
function has been a no-op since Libevent 2.0.4-alpha, it is safe
for us to just stop calling it. Fixes bug 40371; bugfix on
0.2.1.7-alpha.
for us to just stop calling it. Fixes bug 40371; bugfix
on 0.2.1.7-alpha.
Changes in version 0.3.5.16 - 2021-08-16
ReleaseNotes
+18 -18
View File
@@ -3,24 +3,24 @@ release of Tor. If you want to see more detailed descriptions of the
changes in each development snapshot, see the ChangeLog file.
Changes in version 0.3.5.17 - 2021-10-26
This version as a major change which is that v2 onion service are now
disabled at the client, service and relay meaning that any tor nodes
running this version and onward will stops supporting v2. This is the
last step into the long deprecation process of onion service version
2. Everyone running an earlier version, whether as a client, a relay,
or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or
0.4.6.8.
The major change in this version is that v2 onion services are now
disabled at the client, service, and relay: any Tor nodes running this
version and onward will stop supporting v2 onion services. This is the
last step in the long deprecation process of v2 onion services.
Everyone running an earlier version, whether as a client, a relay, or
an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
or 0.4.6.8.
o Major feature (onion service v2, backport from 0.4.5.11):
- See https://blog.torproject.org/v2-deprecation-timeline for
details on how to transition from v2 to v3.
- The control port command HSFETCH and HSPOST don't allow version 2
as well. It is also not possible to create a v2 service with
ADD_ONION.
- Tor does NOT allow anymore to create v2 services, to connect as a
client to a v2 service and for a relay to be a v2 HSDir or
introduction point. This effectively disable onion service version
2 tor wide. Closes 40476.
- The control port commands HSFETCH and HSPOST no longer allow
version 2, and it is no longer possible to create a v2 service
with ADD_ONION.
- Tor no longer allows creating v2 services, or connecting as a
client to a v2 service. Relays will decline to be a v2 HSDir or
introduction point. This effectively disables onion service
version 2 Tor-wide. Closes ticket 40476.
o Minor features (bridge, backport from 0.4.6.8):
- We now announce the URL to Tor's new bridge status at
@@ -28,15 +28,15 @@ Changes in version 0.3.5.17 - 2021-10-26
bridge relay. Closes ticket 30477.
o Minor features (fallbackdir):
- Regenerate fallback directories for October 2021. Close
- Regenerate fallback directories for October 2021. Closes
ticket 40493.
o Minor bugfixes (compatibility, backport from 0.4.6.8):
- Fix compatibility with the most recent Libevent versions, which no
longer have an evdns_set_random_bytes() function. Because this
longer have an evdns_set_random_bytes() function. Because this
function has been a no-op since Libevent 2.0.4-alpha, it is safe
for us to just stop calling it. Fixes bug 40371; bugfix on
0.2.1.7-alpha.
for us to just stop calling it. Fixes bug 40371; bugfix
on 0.2.1.7-alpha.
Changes in version 0.3.5.16 - 2021-08-16