Update to tor 0.4.8.12

[svengo]

https://forum.torproject.org/t/stable-release-0-4-8-12/13060

Here is the ChangeLog.

Changes in version 0.4.8.12 - 2024-06-06
This is a minor release with couple bugfixes affecting conflux and logging.
We also have the return of faravahar directory authority with new keys and
address.

• Minor feature (dirauth):
  • Add back faravahar with a new address and new keys. Closes 40689.
• Minor features (fallbackdir):
  • Regenerate fallback directories generated on June 06, 2024.
• Minor features (geoip data):
  • Update the geoip files to match the IPFire Location Database, as
    retrieved on 2024/06/06.
• Minor bugfix (circuit):
  • Remove a log_warn being triggered by a protocol violation that
    already emits a protocol warning log. Fixes bug 40932; bugfix
    on 0.4.8.1-alpha.
• Minor bugfixes (conflux):
  • Avoid a potential hard assert (crash) when sending a cell on a
    Conflux set. Fixes bug 40921; bugfix on 0.4.8.1-alpha.
  • Make sure we don't process a closed circuit when packaging data.
    This lead to a non fatal BUG() spamming logs. Fixes bug 40908;
    bugfix on 0.4.8.1-alpha.

Summary by CodeRabbit

• Chores
  • Updated Docker container for running a Tor node to version 0.4.8.12.
• Documentation
  • Updated README to reflect the new Tor node version 0.4.8.12.

[coderabbitai]

Walkthrough

The recent update involves a minor version bump for the Tor software used in the Docker container. Specifically, the Tor version has been updated from 0.4.8.11 to 0.4.8.12. This change is reflected in the Dockerfile and mentioned in the README.md file. There are no alterations to the declarations of exported or public entities beyond this version update.

Changes

Files	Change Summary
Dockerfile	Updated TOR_VERSION from 0.4.8.11 to 0.4.8.12
README.md	Updated documentation to reflect the new Tor version

Poem

🐰

A Dockerfile with Tor anew,
From 0.4.8.11 to .12 we flew,
Secure and swift, through nodes we glide,
With every update, more fortified.
In README's lines, the change does show,
Onward we march, with Tor aglow.
🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

Dockerfile (1)

Line range hint 9-9: Consider using WORKDIR for clarity, pinning versions in apk add, and using --no-cache for apk to optimize the build process and ensure reproducibility.

- apk update && \
- apk add \
+ apk add --no-cache \
    curl=7.79.1 \
    gettext=0.21 \
    libcap=2.44 \
    libevent=2.1.12 \
    su-exec=0.2 \
    xz-libs=5.2.5 \
    zlib=1.2.11 \
    zstd-libs=1.4.9 \

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d3a1710 and fc789ea.

Files selected for processing (2)

• Dockerfile (1 hunks)
• README.md (1 hunks)

Additional context used

Hadolint

Dockerfile

[warning] 9-9: Use WORKDIR to switch to a directory (DL3003)

---

[warning] 9-9: Pin versions in apk add. Instead of apk add <package> use apk add <package>=<version> (DL3018)

---

[info] 9-9: Double quote to prevent globbing and word splitting. (SC2086)

---

[info] 9-9: Use the --no-cache switch to avoid the need to use --update and remove /var/cache/apk/* when done installing packages (DL3019)

LanguageTool

README.md

[uncategorized] ~29-~29: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...sponding Dockerfile links - [latest, 0.4.8.12](https://github.com/svengo/d...

Additional comments not posted (2)

Dockerfile (1)

4-4: Updated TOR_VERSION to 0.4.8.12 aligns with the PR's objective.

README.md (1)

29-29: Updated Docker tag to 0.4.8.12 correctly reflects the new Tor version as per the Dockerfile update.

Tools

LanguageTool

[uncategorized] ~29-~29: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...sponding Dockerfile links - [latest, 0.4.8.12](https://github.com/svengo/d...