public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: "IPFire: Development" <development@lists.ipfire.org>
Subject: [PATCH] Tor: Update to 0.4.8.19
Date: Wed, 8 Oct 2025 20:49:00 +0000	[thread overview]
Message-ID: <e86074e4-2e76-4fdc-8f1a-3b1f83e45e52@ipfire.org> (raw)

Changes in version 0.4.8.19 - 2025-10-06
  This release fixes two major bugfixes for a LibreSSL issue and a flow control
  C-tor specific problem (not protocol). We strongly recommend you upgrade as
  soon as possible.

  o Major bugfixes (client, TLS):
    - Fix some clients not being able to connect to LibreSSL relays.
      Fixes bug 41134; bugfix on 0.4.8.17

  o Major bugfixes (stream flow control performance):
    - Use a 5 ms grace period to allow an edge connection to flush its
      stream data to the socket before sending an XOFF. This
      significantly reduces the number of XON/XOFF messages sent when
      (1) the application is reading stream data at a fast rate, and (2)
      when conflux is enabled. Fixes part of bug 41130; bugfix
      on 0.4.7.2-alpha

  o Minor features (fallbackdir):
    - Regenerate fallback directories generated on October 06, 2025.

  o Minor features (geoip data):
    - Update the geoip files to match the IPFire Location Database, as
      retrieved on 2025/10/06.

  o Minor bugfix (process):
    - Avoid closing all possible FDs when spawning a process (PT). On
      some systems, this could lead to 3+ minutes hang. Fixes bug 40990;
      bugfix on 0.3.5.1-alpha.

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
---
 lfs/tor | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/tor b/lfs/tor
index af16cc982..09c965c03 100644
--- a/lfs/tor
+++ b/lfs/tor
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = Anonymizing overlay network for TCP (The onion router)
 
-VER        = 0.4.8.18
+VER        = 0.4.8.19
 
 THISAPP    = tor-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = tor
-PAK_VER    = 90
+PAK_VER    = 91
 
 DEPS       = libseccomp
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 8a2ff369d3b29557a4bb3018dcc5c17b04e459626d23a44bed2968c938a4073ff85c88f734b8f732273197cbb173b70906b4f553db7a432cfbefad73329f6349
+$(DL_FILE)_BLAKE2 = 298612a737a3c035de266549cae911ba709f8c261fe8856f9eff6b7a72b7a71d99e91d1d20dbb6f1c10c9c8d42778423d7a96348303006987dd43fa3888699d8
 
 install : $(TARGET)
 
-- 
2.51.0


                 reply	other threads:[~2025-10-08 20:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e86074e4-2e76-4fdc-8f1a-3b1f83e45e52@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox