From: "André Batista" <nandre@riseup.net>
To: Michael Ford <fanquake@gmail.com>
Cc: 65489@debbugs.gnu.org
Subject: [bug#65489] [PATCH] gnu: tor: Update to 0.4.8.4.
Date: Wed, 30 Aug 2023 21:10:14 -0300 [thread overview]
Message-ID: <ZO_aK6Sj9Cwo3_ox@andel> (raw)
In-Reply-To: <CAFyhPjVD5XozuqUTN=8CqU5pT3-p+jw+OouaO_MSc8vCp673YA@mail.gmail.com>
Hi Michael!
The Tor Project has released v0.4.8.5, so I guess we can skip
v0.4.8.4. Would you care to send a new version of your patch?
Also, Tor v0.4.8.x has introduced a new PoW feature which is useful
for Onion Service operators and users during those all too common
DDoS attempts on the network. However, the feature is disabled by
default because the code was GPL'd. So, in order to enable it for
Guix users - whom I think won't have an issue with GPL code ;) -, you
need to change the current package definition configure flags and add
"--enable-gpl", otherwise we will be missing on this.
Moreover, I'm running the tor-client package and have hit on core/tor
issue #40848[1], since upgrading to v0.4.8.5. Apparently it's a
pretty harmless bug assertion which Alexander Færøy solved [2] by
just removing the bug assertion. Nonetheless, I think it's best if we
also include that patch on Guix, otherwise there may be future
repeated questions from guix users once they start seeing it show up
on system logs.
WDYT?
Cheers!
1 - https://gitlab.torproject.org/tpo/core/tor/-/issues/40848
2 - https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/752
next prev parent reply other threads:[~2023-08-31 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:58 [bug#65489] [PATCH] gnu: tor: Update to 0.4.8.4 Michael Ford
2023-08-31 0:10 ` André Batista [this message]
2023-09-01 7:31 ` Michael Ford
2023-09-01 14:46 ` André Batista
2023-09-14 14:43 ` Ludovic Courtès
2023-09-14 14:45 ` bug#65489: " Ludovic Courtès
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=ZO_aK6Sj9Cwo3_ox@andel \
--to=nandre@riseup.net \
--cc=65489@debbugs.gnu.org \
--cc=fanquake@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.