mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
Release as 1.1.0-pre1
This commit is contained in:
1 parent
451b9b4c28
commit
532408a1b4
8 files changed
+114
-28
No files matched your search
@@ -1,13 +1,22 @@
|
||||
3proxy-1.0.0 Released August, 22 2026
|
||||
3proxy-1.1.0-pre1 Released October, 24 2026
|
||||
|
||||
No changes in 3proxy code, this release only changes how packages are built, signed and published.
|
||||
|
||||
! Fix: TLS, PCRE2 and PAM support was silently left out when 3proxy was built on a system whose /bin/sh is not dash, which is every RPM based distribution and macOS; the library checks built their test program with echo and escape sequences, which only dash expands, so every check failed and the features were dropped without a diagnostic
|
||||
! Fix: rpm packages were built on Ubuntu and required glibc 2.38, libssl.so.3 and libpcre2-8, which no RPM based distribution provides, so they could not be installed anywhere; they are built against AlmaLinux 8, 9 and 10 now and carry an el8, el9 or el10 tag, covering RHEL, AlmaLinux, Rocky and CentOS Stream of the same version
|
||||
! Fix: the rpm package depended on its own interpreter, /bin/3proxy, taken from the first line of the installed configuration file, and could not be installed on el9 or el10 because rpm resolves that dependency to /usr/bin/3proxy
|
||||
! Fix: deb packages required glibc 2.38 and libssl3t64 and installed on Ubuntu 24.04 and newer only; they are built against Ubuntu 22.04 now and install on Ubuntu 22.04 and later as well as Debian 12 and later
|
||||
+ Signed apt and dnf repositories are published at https://3proxy.org/repo/ in two channels: current, built from the master branch, and lts, built from the 0.9 branch; packages and repository metadata are both signed
|
||||
+ Release binaries are published with SHA256 checksums, an OpenPGP signature and a GitHub build provenance attestation; docker images are signed and attested as well
|
||||
+ The release signing key is an RSA-4096 key published as 3proxy-release-key.asc in the repository; rpm 4.14 and earlier can not import an Ed25519 key at all, which would leave RHEL 8 and its derivatives unable to verify anything
|
||||
+ Packages are reproducible: rebuilding a release produces byte identical deb and rpm files, every timestamp is derived from the build date recorded for the release
|
||||
- 32-bit ARM (armhf) is published as a deb package only, Enterprise Linux has no 32-bit ARM build
|
||||
! Fix: a connect back service (-r) replaced by a configuration reload went on waiting up to 60 seconds for the go-ahead, holding a slot and a thread, and every reload left another connection in the queue of the far side (-R); a connection the -r side closed cost the -R side a client
|
||||
! Fix: numbered traffic counters were reset by a configuration reload when no counter file was used
|
||||
+ Configuration reload is atomic: a configuration with an error is refused and the one in force keeps running; a new service on the same address, network namespace and device takes over the old service's listening TCP or UDP socket, so no connection is refused or lost and UDP sessions go on; connections of the old services are re-authenticated against the new configuration (unless noforce), and closed if their service was removed or has no free slot; FTP commands and data connections are authorized by the rules in force
|
||||
+ Services of one configuration on one address share its listening socket; the admin services page shows the clients and traffic of each listening socket, kept across reloads
|
||||
+ Logs: each log is opened once and shared by every service using it, kept open over a reload while used and closed once unused; -l takes the same arguments as log; each log is written by a thread of its own from a queue, so a client never waits for a slow log (ODBC, RADIUS, a full disk); a record which finds the queue full is dropped, and dropped records and log failures are reported
|
||||
+ minlogqueue / maxlogqueue: the records a log's queue keeps room for and holds at most (64 and 4096 by default)
|
||||
+ ODBC log: the datasource alone names the log, username and password are its parameters, never shown in messages; a log with the same datasource and other credentials reconnects with them
|
||||
+ threadpool <max_idle> [<idle_seconds>]: a thread whose connection ended waits for the next one of any service, with its memory, instead of ending; by default up to 32 threads per running service; the admin services page shows the pool
|
||||
+ defaultresolve / sysresolve / fakeresolve apply to the services started after them: defaultresolve (the default) uses the name servers in force, sysresolve the system routines (the C library), as without nserver before
|
||||
+ timeouts, filtermaxsize, parentretries, delimchar and maxseg apply to the services started after them, so services can have values of their own
|
||||
+ ssl_ktls / ssl_noktls: kernel TLS (Linux, FreeBSD) with OpenSSL 3.0 or later built with kernel TLS; splice() works over kernel TLS
|
||||
+ -s:MIN,STREAK,SMALL tunes when the automatic splice() mode splices a direction and when it copies again
|
||||
+ filtermaxsize 0 removes the limit
|
||||
+ UDP services (udppm, dnspr) run in one thread each, with no thread per client, using epoll on Linux; dnspr waits for name servers without holding a thread
|
||||
+ Connection buffers are allocated with the connection structure, together with the thread pool fewer allocations per connection
|
||||
+ Build-time defaults: -DLOGQUEUEMIN, -DLOGQUEUEMAX, -DDEFAULT_POOLMAX, -DPOOLPERSERVICE, -DDEFAULT_POOLTIMEOUT, -DDEFAULT_MAXCHILD
|
||||
- splice() in the automatic mode is the default on Linux (-s0 turns it off); a service with data filters, or beginning or ending TLS without kernel TLS both ways, does not splice
|
||||
- -ni / -ne (Linux network namespaces): threads stay in the namespace 3proxy was started in and enter the configured one only to create a socket; -ni covers the socket SOCKS UDP ASSOCIATE talks to the client on, -ne SOCKS BIND, the UDP sockets towards the destination and the connect back sockets; name resolution, logging and RADIUS stay in the original namespace; the path is opened when the service line is read, and one which is not a network namespace stops the service from starting
|
||||
- Without nserver, names are resolved by 3proxy's own resolver with the system's name servers (up to 3 from /etc/resolv.conf, on Windows from the registry), answering names of the hosts file first, instead of the C library; both are checked for changes every 5 seconds, nsrecord takes precedence over the hosts file and dnspr forwards queries to them; the C library is used if no name server is found, or with sysresolve
|
||||
- Dial on demand is removed: dialer is accepted and ignored
|
||||
Reference in new issue
Block a user