A lightweight but incredibly powerful and feature-rich BitTorrent tracker. Supports UDP + HTTP(S) and a private tracker mode.

Overview

Torrust Tracker

Test

Project Description

Torrust Tracker is a lightweight but incredibly powerful and feature-rich BitTorrent tracker made using Rust.

Features

  • UDP server
  • HTTP (optional SSL) server
  • Private & Whitelisted mode
  • API Hooks
  • Torrent whitelisting
  • Peer authentication using time-bound keys

Implemented BEPs

  • BEP 15: UDP Tracker Protocol for BitTorrent
  • BEP 23: Tracker Returns Compact Peer Lists
  • BEP 27: Private Torrents
  • BEP 41: UDP Tracker Protocol Extensions
  • BEP 48: Tracker Protocol Extension: Scrape

Getting Started

You can get the latest binaries from releases or follow the install from scratch instructions below.

Install From Scratch

  1. Clone the repo.
git clone https://github.com/torrust/torrust-tracker.git
cd torrust-tracker
  1. Build the source code.
cargo build --release
  1. Copy binaries: torrust-tracker/target/torrust-tracker to a new folder.

Usage

  1. Navigate to the folder you put the torrust-tracker binaries in.

  2. Run the torrust-tracker once to create the config.toml file:

./torrust-tracker
  1. Edit the newly created config.toml file in the same folder as your torrust-tracker binaries according to your liking. See configuration documentation.

  2. Run the torrust-tracker again:

./torrust-tracker

Tracker URL

Your tracker will be udp://tracker-ip:port or https://tracker-ip:port depending on your tracker mode. In private mode, tracker keys are added after the tracker URL like: https://tracker-ip:port/tracker-key.

Credits

This project was a joint effort by Nautilus Cyberneering GmbH and Dutch Bits.

Comments
  • Re-implement connection ID generation for UDP tracker

    Re-implement connection ID generation for UDP tracker

    TODO:

    • [x] Add test for verify_connection_id
    • [x] Move get_connection_id to udp module.
    • [x] Move current_time to clock module.
    • [x] Add "pepper" to the implementation: https://github.com/torrust/torrust-tracker/pull/60#issuecomment-1214172679
    • [x] Write more documentation. Something like my comment here. I think I'm going to use the Rust /// inline documentation in this case.
    • [x] Reimplement connection ID generation function using encryption as proposed by @da2ce7 here.
    • [x] Use the function verify_connection_id to verify the UDP announce request.
    • [x] Refactor handlers to avoid creating the EncryptedConnectionIdIssuer multiple times.
    • [x] Generate SALT when the server starts. We call it SERVER_SCRET now.
    • [x] Generate a random secret. We are using a fixed one.
    • [x] Refactor code to include some improvements from @WarmBeer PR.
    • [x] Change the Blowfish crate. The one we are using is deprecated.
    • [ ] Refactor code to include some improvements from @da2ce7 PR.

    REMOVED FROM TODO:

    • [x] Change one of the tests where I use "sleep" instead of mocking time. We need to implement a new serializer where we can inject the time. It's out of the scope of this PR and it's only ten milliseconds the delay introduced in the test execution.
    opened by josecelano 69
  • Torrust scrape has packed data errors and is not properly formatted

    Torrust scrape has packed data errors and is not properly formatted

    Hello, there seems to be an error with packed data when scraping announce both udp and http/s.

    The format should be d5:filesd20, but on gbitt and torrust it is random, sometimes it is d5:filesd50, d5:filesd54, etc. Thats why almost all scrapers returns invalid data for info hash.

    Seems like it is using aquatic source for scraping, but aquatic returns correct bytes of 20, where torrust doesn't.

    @Power2All @WarmBeer

    opened by dev1z 20
  • Full docker support

    Full docker support

    This is a re-work of PR-55 adding more features.

    UPDATE ON: 2022/12/16

    TASKS

    • [x] Docker image
    • [X] Publish the docker image manually (https://hub.docker.com/repository/docker/josecelano/torrust-tracker)
    • [x] Cache for dependencies in Dockerfile is not working. It compiles all the dependencies every time you build the image.
    • [x] Workflow to publish new docker images when new semver tags are created.
    • [x] Fix broken test after moving database to storage/database dir.
    • [x] Deploy sample app using SQLite with docker on Azure.
    • [x] Docker compose configuration using MySQL instead of SQLite for development
    • [x] Docker compose configuration using MySQL instead of SQLite for production. Moved to another repo.
    • [x] Deploy sample app using MySQL with docker compose on Azure. Moved to another repo.

    SUBTASKS (deploy with docker)

    This option is a deployment to ACI using only one container with SQLite and no HTTPS.

    • [x] Create a certificate with Let's Encrypt and use Rust (no Nginx). DISCARDED (I'll do it in the docker-compose version)
    • [x] Enable HTTPS for the API.
    • [x] Error duplciate port 6969.

    SUBTASKS (deploy with docker-compose)

    • [x] Create a certificate with Let's Encrypt and use Nginx. DISCARDED for this PR.
    • [x] Auto-renew certificate with certbot. DISCARDED for this PR.
    • [x] Use MySQL instead of SQLite

    REQUIREMENTS

    • Multistage builds with slim/alpine images for production
    • Do not execute the container with the root user.
    • Try to cache cargo dependencies with cargo-chef
    • Build static rust binaries for x86_64 linux environments (without other system library dependencies)
    • Consider using certificates for localhost too?
    • Use Nginx with certbot on Production for HTTPS.
    • Auto-renew certificate with cerbot or Nginx docker image with auto-renew.
    • Use Github Actions cache for docker cache: https://docs.docker.com/build/building/cache/backends/gha/
    • User semver for docker image tags.

    OPTIONAL

    • [x] .devcontainer configuration for GitHub Codespaces. DISCARDED for this PR.
    • [x] docker compose configuration for docker env environments. DISCARDED for this PR.

    LINKS

    • https://github.com/docker/awesome-compose
    • https://hub.docker.com/repository/docker/josecelano/torrust-tracker
    • https://docs.docker.com/cloud/aci-integration/
    • https://docs.docker.com/desktop/dev-environments/set-up/
    • https://github.com/clux/muslrust
    • https://github.com/LukeMathWalker/cargo-chef
    • https://letsencrypt.org/docs/certificates-for-localhost/
    • https://medium.com/@mccode/understanding-how-uid-and-gid-work-in-docker-containers-c37a01d01cf
    • https://github.com/docker/awesome-compose/tree/master/react-rust-postgres
    • https://kerkour.com/rust-small-docker-image
    opened by josecelano 19
  • Error only .torrent files

    Error only .torrent files

    I'm not sure what I may be missing. Everything seem to be working and all categories etc. show up. Account created access seem to work. Doing a test with the debian net ISO and or any other torrent and I get " only .torrent files can be uploaded" even though they are .torrent files.

    opened by Pupwiz 16
  • Docker Support

    Docker Support

    opened by Zibbp 16
  • Refactor: re-implement connection id for UDP tracker

    Refactor: re-implement connection id for UDP tracker

    BEP 15: https://www.bittorrent.org/beps/bep_0015.html

    This is what the BEP 15 says about the connection ID:

    UDP connections / spoofing In the ideal case, only 2 packets would be necessary. However, it is possible to spoof the source address of a UDP packet. The tracker has to ensure this doesn't occur, so it calculates a value (connection_id) and sends it to the client. If the client spoofed it's source address, it won't receive this value (unless it's sniffing the network). The connection_id will then be send to the tracker again in packet 3. The tracker verifies the connection_id and ignores the request if it doesn't match. Connection IDs should not be guessable by the client. This is comparable to a TCP handshake and a syn cookie like approach can be used to storing the connection IDs on the tracker side. A connection ID can be used for multiple requests. A client can use a connection ID until one minute after it has received it. Trackers should accept the connection ID until two minutes after it has been send.

    And this is the current implementation:

    pub fn get_connection_id(remote_address: &SocketAddr) -> ConnectionId {
        match std::time::SystemTime::now().duration_since(std::time::UNIX_EPOCH) {
            Ok(duration) => ConnectionId(((duration.as_secs() / 3600) | ((remote_address.port() as u64) << 36)) as i64),
            Err(_) => ConnectionId(0x7FFFFFFFFFFFFFFF),
        }
    }
    

    Originally posted by @josecelano in https://github.com/torrust/torrust-tracker/issues/60#issuecomment-1210961955

    refactor 
    opened by josecelano 9
  • [proposal] Create an installer with a flag (argument)

    [proposal] Create an installer with a flag (argument)

    When you run the tracker the first time, you see this output:

    No config file found.
    Creating config file..
    thread 'main' panicked at 'Please edit the config.TOML in the root folder and restart the tracker.', src/main.rs:22:13
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
    

    Running the tracker without the setting file has a side effect. It creates a setting file with the default configuration.

    $ cat config.toml
    log_level = "info"
    mode = "public"
    db_driver = "Sqlite3"
    db_path = "data.db"
    announce_interval = 120
    min_announce_interval = 120
    max_peer_timeout = 900
    on_reverse_proxy = false
    external_ip = "0.0.0.0"
    tracker_usage_statistics = true
    persistent_torrent_completed_stat = false
    inactive_peer_cleanup_interval = 600
    remove_peerless_torrents = true
    
    [[udp_trackers]]
    enabled = false
    bind_address = "0.0.0.0:6969"
    
    [[http_trackers]]
    enabled = false
    bind_address = "0.0.0.0:6969"
    ssl_enabled = false
    ssl_cert_path = ""
    ssl_key_path = ""
    
    [http_api]
    enabled = true
    bind_address = "127.0.0.1:1212"
    
    [http_api.access_tokens]
    admin = "MyAccessToken"
    

    I suggest showing a message like this:

    No config file found: "config.toml".
    You can create the default settings file running: cargo run --bin install
    

    That "install" binary could be extended in the feature to be an installation assistant if you run it in interactive mode.

    But the main reason for this change is I'm working on setting up docker configuration to automate deployments for the Turrust tracker and running a process that returns an error that could lead to errors while building docker images or others tasks.

    On the other hand, I always prefer to be explicit about side effects. Besides, showing an error the first time you run a tracker could make people think the application is not good.

    If you do not like that approach, the second option could be to ask the user if they want to create that file, but I do not like that option because it forces the app to be always interactive. We should have added an option to avoid that question in this case and return an error message with an error return value (not a panic message).

    enhancement 
    opened by josecelano 8
  • Make tracker statistics optional again

    Make tracker statistics optional again

    Commit 7abe0f5bde1e209553d1a1e2d6fe644cd46a9395 introduced an unwanted change. Thread for statistics is always created regardless configuration.

    This commit reverts that change. The config option:

    config.tracker_usage_statistics

    defines wether the statistics should be enabled or not.

    opened by josecelano 8
  • Publish it on crates.io

    Publish it on crates.io

    Wouldn't it be useful to publish it on https://crates.io/?

    I would like to write more documentation for the package. For example, for API endpoints like this:

    image

    If we do that, we can automatically have online documentation on https://docs.rs/.

    If for some reason, we do not want to publish it yet, we could deploy the documentation to GitHub Pages.

    documentation 
    opened by josecelano 8
  • Udp: Basic Connection Cookie Implementation

    Udp: Basic Connection Cookie Implementation

    This implementation is very basic and not optimal. However it should be secure and works as a proof of concept.

    It works by testing many possible connection cookies for each time extent (a quantified period of time), until one matches. If there are no matches, then the cookie is either expired or otherwise invalid.

    opened by da2ce7 7
  • Clock: Time Extent, Maker, and Associated Traits

    Clock: Time Extent, Maker, and Associated Traits

    TimeExtent is a simple structure that contains base increment (duration), and amount (a multiplier for the base the base increment). The resulting product of the base and the multiplier is the total duration of the time extent.

    TimeExtentClock is a helper that generates time extents based upon the increment length and the time of the clock, this clock is specialised according to the test predicate with the DefaultClockExtentMaker type.

    These modules will be used by the later connection cookie implementation.

    opened by da2ce7 7
  • A database should be optional

    A database should be optional

    The tracker only needs a database if it wants to persist torrent statistics and private tracker keys between reboots. In all other cases a database should not be necessary.

    opened by WarmBeer 0
  • Setup tracker and seeder in local env

    Setup tracker and seeder in local env

    Hey there!

    Is there a document that describes how to set up a tracker and a local client to seed a specific file/folder? In other words, how can I configure a tracker and a seeder-client on my local machine to share a specific file?

    opened by Almaz-KG 0
  • Fix `opaque type` warnings

    Fix `opaque type` warnings

    When you run the application or the tests you see these warnings:

    $ cargo test
       Compiling torrust-tracker v2.3.0 (/home/josecelano/Documents/github/committer/josecelano/torrust/torrust-tracker)
    warning: opaque type `impl warp::Filter + Clone + warp::filter::FilterBase<Extract = impl Reply, Error = Rejection>` does not satisfy its associated type bounds
      --> src/api/routes.rs:50:63
       |
    50 | pub fn routes(tracker: &Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply, Error = warp::Rejection> + Clone {
       |                                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
      ::: /home/josecelano/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.3/src/filter/mod.rs:40:19
       |
    40 |     type Extract: Tuple; // + Send;
       |                   ----- this associated type bound is unsatisfied for `impl Reply`
       |
       = note: `#[warn(opaque_hidden_inferred_bound)]` on by default
    help: add this bound
       |
    50 | pub fn routes(tracker: &Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply + warp::generic::Tuple, Error = warp::Rejection> + Clone {
       |                                                                                          ++++++++++++++++++++++
    
    warning: opaque type `impl warp::Filter + Clone + warp::filter::FilterBase<Extract = impl Reply, Error = Infallible>` does not satisfy its associated type bounds
      --> src/http/routes.rs:12:62
       |
    12 | pub fn routes(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply, Error = Infallible> + Clone {
       |                                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
      ::: /home/josecelano/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.3/src/filter/mod.rs:40:19
       |
    40 |     type Extract: Tuple; // + Send;
       |                   ----- this associated type bound is unsatisfied for `impl Reply`
       |
    help: add this bound
       |
    12 | pub fn routes(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply + warp::generic::Tuple, Error = Infallible> + Clone {
       |                                                                                         ++++++++++++++++++++++
    
    warning: opaque type `impl warp::Filter + Clone + warp::filter::FilterBase<Extract = impl Reply, Error = Rejection>` does not satisfy its associated type bounds
      --> src/http/routes.rs:19:60
       |
    19 | fn announce(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply, Error = Rejection> + Clone {
       |                                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
      ::: /home/josecelano/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.3/src/filter/mod.rs:40:19
       |
    40 |     type Extract: Tuple; // + Send;
       |                   ----- this associated type bound is unsatisfied for `impl Reply`
       |
    help: add this bound
       |
    19 | fn announce(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply + warp::generic::Tuple, Error = Rejection> + Clone {
       |                                                                                       ++++++++++++++++++++++
    
    warning: opaque type `impl warp::Filter + Clone + warp::filter::FilterBase<Extract = impl Reply, Error = Rejection>` does not satisfy its associated type bounds
      --> src/http/routes.rs:29:58
       |
    29 | fn scrape(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply, Error = Rejection> + Clone {
       |                                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
      ::: /home/josecelano/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.3/src/filter/mod.rs:40:19
       |
    40 |     type Extract: Tuple; // + Send;
       |                   ----- this associated type bound is unsatisfied for `impl Reply`
       |
    help: add this bound
       |
    29 | fn scrape(tracker: Arc<tracker::Tracker>) -> impl Filter<Extract = impl warp::Reply + warp::generic::Tuple, Error = Rejection> + Clone {
       |                                                                                     ++++++++++++++++++++++
    
    warning: `torrust-tracker` (lib) generated 4 warnings
    warning: `torrust-tracker` (lib test) generated 4 warnings (4 duplicates)
    

    We are going to replace Warp with Axum, so it may not make sense to fix them.

    opened by josecelano 0
  • Workflow to publish crate on crates.io

    Workflow to publish crate on crates.io

    Workflow to publish the crate on crates.io.

    It only works if the secret CRATES_TOKEN exists in the crates-io-torrust environment.

    Since crates.io does not support scoped tokens, we can publish the crate using a fork where the crate owners can set up their crates.io tokens without sharing them with other maintainers.

    opened by josecelano 1
  • Publish it on crates.io

    Publish it on crates.io

    Discussed in https://github.com/torrust/torrust-tracker/discussions/132

    Originally posted by josecelano August 10, 2022 Wouldn't it be useful to publish it on https://crates.io/?

    I would like to write more documentation for the package. For example, for API endpoints like this:

    image

    If we do that, we can automatically have online documentation on https://docs.rs/.

    If for some reason, we do not want to publish it yet, we could deploy the documentation to GitHub Pages.

    documentation workflow 
    opened by josecelano 0
Releases(v2.3.1)
  • v2.3.1(May 16, 2022)

  • v2.3.0(May 9, 2022)

  • v2.2.1(Mar 17, 2022)

    Version 2.2.0

    New Features:

    • Added support for multiple UDP and HTTP blocks: https://github.com/torrust/torrust-tracker/commit/f596f226e9e1dd5662ba5f0079f0469d89e4f76d
    • Added tracker stats tracking: https://github.com/torrust/torrust-tracker/commit/f6eb8533909678c6f5547a9d1a95b26b81978c68
    • Partially implemented persistent torrents saving/loading: https://github.com/torrust/torrust-tracker/commit/ab605455ddb0861d4059dc60e4f37c384e5b3527

    Changes:

    • Some performance optimizations.
    • Udp and http server now gracefully shutdown: https://github.com/torrust/torrust-tracker/commit/f46df3845e8ac7828db93bad17a9bae5343ee351
    • Added max peer timeout config option: https://github.com/torrust/torrust-tracker/commit/ca2d118a573b6156ea1812340db4c6604dae4073
    • Changed udp max packet size from 65535 to 1496: https://github.com/torrust/torrust-tracker/commit/f9eaa10ba86334dbf918a798e4d48a8d711b0bfe

    Fixes:

    • Fixed errors during parsing of the peer_id from announce_requests.
    • Fixed http announce request error when optional fields were left out: https://github.com/torrust/torrust-tracker/commit/9637661f10c52507884c0dc9b809d22ebcea9d50
    • Fixed errors not displaying in bencoded format: https://github.com/torrust/torrust-tracker/commit/f2125f279087a9e4beb90c38b599ac02ac5497bb
    • Fixed error after udp announcing with no other peers then the client: https://github.com/torrust/torrust-tracker/commit/b0417a3d5cf7074874dd13a9e06dc6fa7c8383ca
    • Fixed returning ipv6 peers to ipv6 clients: https://github.com/torrust/torrust-tracker/commit/b34f56405824ee85bfbef9c942214934adf4979e
    • Fixed http reverse proxy client ip determination: https://github.com/torrust/torrust-tracker/commit/2e25d537b197efb82249984f26fdd36a7d28e6a1
    Source code(tar.gz)
    Source code(zip)
Owner
Torrust
Tools to host your own online torrent database.
Torrust
🖥 A feature rich terminal UI file transfer and explorer with support for SCP/SFTP/FTP/S3

?? A feature rich terminal UI file transfer and explorer with support for SCP/SFTP/FTP/S3

Christian Visintin 574 Jan 5, 2023
⏳ trackie is a private, daemon-less time tracker for your CLI.

⏳ trackie `trackie` is a private, daemon-less time tracker running in your CLI. Trackie offers an easy CLI to track the time you spent on your various

Christoph Loy 40 Dec 14, 2022
Terminal based, feature rich, interactive SQL tool

datafusion-tui (dft) DataFusion-tui provides a feature rich terminal application, built with tui-rs, for using DataFusion (and eventually Ballista). I

null 49 Dec 24, 2022
Fast, minimal, feature-rich, extended formatting syntax for Rust!

Formatting Tools Fast, minimal, feature-rich, extended formatting syntax for Rust! Features include: Arbitrary expressions inside the formatting brace

Casper 58 Dec 26, 2022
CLI tool for generating a summary of recent github activity for people who are incredibly forgetful

CLI tool for generating a summary of recent github activity for people who are incredibly forgetful but still need to give weekly status updates to their boss without getting depressed and convincing themselves they did nothing because they can't remember what they did!

Jane Lusby 50 Dec 23, 2022
Estratto is a powerful and user-friendly Rust library designed for extracting rich audio features from digital audio signals.

estratto 〜 An Audio Feature Extraction Library estratto is a powerful and user-friendly Rust library designed for extracting rich audio features from

Amber J Blue 5 Aug 25, 2023
Super-lightweight Immediate-mode Embedded GUI framework, based on the awesome embedded-graphics library. Written in Rust.

Kolibri - A GUI framework made to be as lightweight as its namesake What is Kolibri? Kolibri is an embedded Immediate Mode GUI mini-framework very str

null 6 Jun 24, 2023
A super simple but lightweight logging library that tries to capture the most important (status) information.

Hackerlog A super simple but lightweight logging library that tries to capture the most important (status) information. The following is supported: Lo

434b 3 Aug 22, 2023
Yet another lightweight and easy to use HTTP(S) server

Raptor Web server Raptor is a HTTP server written in Rust with aims to use as little memory as possible and an easy configuration. It is built on top

Volham 5 Oct 15, 2022
A fast and lightweight HTTP server implementation in Rust.

server_nano A tiny, fast, and friendly web server written in rust and inspired by express. It uses may to coroutines Usage First, add this to your Car

Jonny Borges 5 May 2, 2023
nvim-oxi provides safe and idiomatic Rust bindings to the rich API exposed by the Neovim text editor.

?? nvim-oxi nvim-oxi provides safe and idiomatic Rust bindings to the rich API exposed by the Neovim text editor. The project is mostly intended for p

Riccardo Mazzarini 655 Jul 13, 2023
🚀 Discord Rich Presence plugin for Neovim written in Rust

?? Cord ?? Cord is a Discord Rich Presence plugin designed for Neovim, written in Rust. ?? Features Lightweight and dependency-free Cross-platform sup

vyfor 39 May 6, 2024
A super simple prompt for Fish shell, just shows git info and Vi mode.

vifi is a portmandeau of 'Vi' and 'Fish', because it's a prompt for Fish shell, primarily focused around showing proper indicators when using Vi key bindings.

Mat Jones 1 Sep 15, 2022
A simple cli tool to help with wordle in hard mode

Wordking A simple cli tool to help with wordle in hard mode. Usage Run wordking cargo run Wordking will ask for your guesses thus far. Provide your gu

Stephen Spalding 2 Feb 1, 2022
An Intel HAXM powered, protected mode, 32 bit, hypervisor addition calculator, written in Rust.

HyperCalc An Intel HAXM powered, protected mode, 32 bit, hypervisor addition calculator, written in Rust. Purpose None ?? . Mostly just to learn Rust

Michael B. 2 Mar 29, 2022
Tricking shells into interactive mode when local PTY's are not available

Remote Pseudoterminals Remote Pseudoterminals or "RPTY" is a Rust library which intercepts calls to the Linux kernel's TTY/PTY-related libc functions

null 135 Dec 4, 2022
easy-to-use immediate mode client side Rust web framework

An immediate mode web frontend library written in Rust. It builds up VDOM for not having to run too many DOM operations, but as it runs every time any

null 22 Dec 17, 2022
Example of an dark-mode toggle button based on progressive enhancement

Leptos Starter Template This is a template for use with the Leptos web framework and the cargo-leptos tool. Creating your template repo If you don't h

Leptos 5 Jan 12, 2023
rp-bf: A library to bruteforce ROP gadgets by emulating a Windows user-mode crash-dump

rp-bf: A library to bruteforce ROP gadgets by emulating a Windows user-mode crash-dump Motivations Oftentimes after hijacking control-flow, the author

Axel Souchet 112 Nov 15, 2024