Repository navigation
v1.7.3
Downloads / 下载
Choose your operating system and architecture. / 按操作系统和架构选择下载。
Client / 客户端
Configure package managers to use MirrorProxy. / 用于配置包管理器的镜像源。
| Architecture / 架构 | Windows | macOS | Linux |
|---|---|---|---|
| x86-64 (64-bit) | EXE · ZIP | TAR.GZ | RPM · TAR.GZ · DEB |
| AArch64 (ARM64) | EXE · ZIP | TAR.GZ | RPM · TAR.GZ · DEB |
Server / 服务端
Self-host the proxy and administration console (Windows/Linux). / 自建代理服务与管理后台(Windows/Linux)。
| Architecture / 架构 | Windows | Linux |
|---|---|---|
| x86-64 (64-bit) | ZIP | RPM · TAR.GZ · DEB |
| AArch64 (ARM64) | ZIP | RPM · TAR.GZ · DEB |
Verify downloads with SHA256SUMS. / 下载后请校验 SHA256SUMS。
— = No package published for this platform. / 此平台暂无安装包。
MirrorProxy v1.7.3
MirrorProxy v1.7.3 makes Windows client and server executables independent of a separately installed Visual C++ Runtime. It also adds discoverable administrator Passkeys and improves verified build reuse.
Highlights
- Statically link the MSVC C/C++ runtime into Windows x64 and ARM64 clients and servers. ZIP packages and standalone client EXEs no longer require installing the VC++ Redistributable. Windows system DLLs remain required.
- Inspect both regular and delay-loaded PE imports, including the executable's architecture, in Windows CI and release packaging. Reject external CRT and OpenSSL DLL dependencies even when the build runner already has those libraries installed. Execute the extracted client with
--versionandlist, and exercise the extracted server's real proxy routes. - Remove the VC++ Runtime dependency from WinGet manifests for 1.7.3 and later. Regenerated manifests for existing releases through 1.7.2 retain their runtime prerequisites; published older assets and hashes are unchanged.
- Allow administrator Passkey sign-in without entering a username when using discoverable credentials. Preserve named authentication for existing security keys and keep Passkey-management errors separate from legacy sign-in guidance.
- Reuse verified frontend artifacts and cache native build dependencies, browser downloads and checksum-pinned GeoIP/Perl inputs. Cache hits still run the required tests; frontend artifacts are verified against the source commit and complete file inventory.
- Build Docker amd64 and ARM64 images on native runners, verify real proxy behavior, and retain digest, SBOM, provenance and signing checks.
- Add a validation-only Release workflow mode that builds and verifies all platform packages without publishing them.
Security and dependency status
This release fixes a Windows loader dependency issue; it does not bundle an external runtime installer. Authentication, authorization, CSRF, SSRF, TLS, quota and audit controls remain enabled.
The frontend dependency versions are unchanged. The official npm audit recheck on 2026-11-06 reports eight low-severity findings propagated from deepmerge 4.3.1, with no moderate, high or critical findings. Upstream has not published a patched deepmerge version. The corrected affected range of GHSA-g3hv-75wg-m249 is >=7.0.0 <11.0.1, so the legacy minimatch 3.1.5 dependency is outside that advisory's scope; this is an advisory correction rather than a package upgrade. Existing narrowly scoped build-tool audit policies remain in place.
Rust dependency audits retain the documented RUSTSEC-2023-0071 and RUSTSEC-2026-0387 exceptions for private/secret operations outside the reviewed OIDC public-key verification path. See SECURITY.md.
Compatibility, upgrade and rollback
Configuration, routes, CLI setup output and SQLite data remain compatible. No manual migration is required. Windows clients remain portable command-line applications; Windows servers run in the foreground, and the install subcommand continues to manage Linux systemd only. The existing platform/package matrix is retained, including macOS clients only.
Download the matching artifact and verify its published SHA-256 checksum before replacing an executable. Preserve configuration, database, cache and GeoIP files, then verify --version and representative real requests after restarting. To roll back, restore the previous executable with the preserved configuration and data; Windows releases through 1.7.2 still require their matching VC++ Runtime.
Publishing this release does not replace an existing production installation.
Verification
Release acceptance requires successful CI and CodeQL for the exact release commit, Windows x64/ARM64 debug and release checks, PE import inspection of packaged executables, client command execution and server protocol smoke. The other gates cover locked Rust formatting, Clippy and tests; frontend tests, build and browser checks; package metadata; administration sessions; and dependency audits with the documented exceptions. The validation-only build precedes the version tag. Published artifact verification checks SHA256SUMS and unpacked executable versions. Docker publication and WinGet repository review have independent completion states.
Full comparison: v1.7.2...v1.7.3