Package: snowflake-client Version: 2.5.1-1+b16 Severity: normal Dear Maintainer,
snowflake-client 2.5.1 is quite outdated today, without features such as "fronts: comma-separated list of front domains" and SQS implemented later. The lack of "fronts" options support can even causes the real domain of the broker being exposed via SNI when snowflake bridge lines (copied from tor browser) contain "fronts=" instead of the old "front=", so I mark the severity of this issue as normal. Instead of adopting the latest version of snowflake-client, this issue might also be resolved by adopting lyrebird, as #1111471 and #1063423 suggested, as lyrebird now combines the functionalities of both client and server of obfs4proxy, snowflake, and more other pluggable transports. -- System Information: Debian Release: forky/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.16.9+deb14-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages snowflake-client depends on: ii libc6 2.41-12 snowflake-client recommends no packages. snowflake-client suggests no packages. -- no debconf information
