3proxy package repository

Signed apt and dnf repositories for 3proxy. Two channels are published:

Channel	Branch	Contents
`lts`	0.9	long term support releases
`current`	master	current stable releases

All packages and all repository metadata are signed with the 3proxy release key, 3proxy-release-key.asc:

pub   rsa4096 2026-08-21 [SC]
      FC12 2144 99FC C7BA 1CFF  6CDC 0312 384E 3A73 940B
uid   3proxy release signing <[email protected]>

Debian, Ubuntu

sudo curl -fsSL https://3proxy.org/repo/3proxy-release-key.asc \
     -o /usr/share/keyrings/3proxy.asc

sudo tee /etc/apt/sources.list.d/3proxy.sources <<EOF
Types: deb
URIs: https://3proxy.org/repo/deb
Suites: lts
Components: main
Signed-By: /usr/share/keyrings/3proxy.asc
EOF

sudo apt update
sudo apt install 3proxy

Use Suites: current for the current stable channel. The Signed-By field accepts an armoured key from apt 2.4 onwards (Debian 12, Ubuntu 22.04). On older releases, convert it first:

sudo gpg --dearmor -o /usr/share/keyrings/3proxy.gpg /usr/share/keyrings/3proxy.asc

and point Signed-By at the .gpg file.

RHEL, Fedora, and derivatives

sudo tee /etc/yum.repos.d/3proxy.repo <<EOF
[3proxy]
name=3proxy \$basearch
baseurl=https://3proxy.org/repo/rpm/lts/el\$releasever/\$basearch/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://3proxy.org/repo/3proxy-release-key.asc
EOF

sudo dnf install 3proxy

Replace lts with current for the current stable channel. Both the packages (gpgcheck) and the repository metadata (repo_gpgcheck) are verified.

Debian packages are built against Ubuntu 22.04 and install on Ubuntu 22.04 and later as well as Debian 12 and later.

Packages are built against AlmaLinux 8, 9 and 10 and are published per Enterprise Linux major version, which is what $releasever selects. They apply equally to RHEL, Rocky and CentOS Stream of the same version. Enterprise Linux has no 32-bit ARM build, so armhf is available as a deb only.

What is in the repository

Only releases that ship a GPG-signed SHA256SUMS file are mirrored. Every package is checksum-verified against a signature made by a published 3proxy key before it is accepted, and is then re-signed with the current release key so that a single imported key covers the whole repository. Releases before signing was introduced carry no signed checksums and are not included; they remain available from the GitHub releases page.