You probably mean PROVIDEr=bitmask. Since the VPN is riseup-vpn intended to connect to riseup's end points, unfortunately this is not an actionable request.
More importantly, the end points for bitmask as mentioned here: https://0xacab.org/leap/bitmask-vpn/-/blob/main/providers/vendor.conf?ref_type=heads#L107 As you may see, all of these are demo end-points. I don't think a distribution package should provide opt to connect to demo end points for users so this is something I can't implement. However, if you want this for your personal usage, feel free to change PROVIDER to bitmask in https://salsa.debian.org/go-team/packages/riseup-vpn/-/blob/debian/sid/debian/rules?ref_type=heads#L23 and use the deb of your own :) On 2024-08-29 13:47, h...@riseup.net wrote: > The quoted commit shows basically it is the vpn client compiled for > VENDOR=riseup that has obfs4 removed, but VENDOR=bitmask not. Would you > be able to compile the vpn client with VENDOR=bitmask and have a try > with obfs4 transport to see if it is working? Thanks. > > On 2024-08-28 18:48, Nilesh Patra wrote: >> Since the commit message explicitly says: >> >> | riseup currently is not having any deployed obfs4 or kcp bridges >> >> I guess it won't connect anyway even if you try to do so via UI. In that >> case, there's nothing that could be done >> maybe backporting a new version soonish? >> >> Since there's no bridge, its not in my control to get it working so I'm >> going w closing this bug. Please re-open if you think >> this is an error from my end. >> >> On 2024-08-28 13:52, h...@riseup.net wrote: >>> Obfs4 transport as a feature may well have been removed at some point >>> during the transition from version 0.21 to 0.24 >>> >>> https://0xacab.org/leap/bitmask-vpn/-/commit/d8350ee89e144970a844605cabe246c35653ce8c >>> >>> https://0xacab.org/leap/bitmask-vpn/-/commit/ccf0bfa4bd02c92e8be9501fdc1a296cece8f564 >>> >>> On 2024-08-18 19:18, Nilesh Patra wrote: >>>> Hello, and sorry for late response >>>> >>>> On Wed, 29 May 2024 23:57:22 +0800 hgj <h...@riseup.net> wrote: >>>>> Package: riseup-vpn >>>>> Version: 0.24.5+ds1-2~bpo12+1 >>>>> Severity: normal >>>>> X-Debbugs-Cc: h...@riseup.net >>>>> >>>>> Dear Maintainer, >>>>> >>>>> I have just upgraded riseup-vpn to the backport version on Debian stable, >>>>> but it >>>>> fails to connect with socks-error, I saw the line >>>>> >>>>> start socks5 proxy 127.0.0.1:8080 >>>> >>>> That's a bit weird. I've had multiple people test it and it works fine for >>>> everyone. >>>> >>>>> in both the verbose log and riseup-vpn >>>>> connection parameters. The following error message repeats itself and >>>>> riseup vpn fails to connect. >>>>> ``` >>>>> 2024/05/29 23:36:12 New connection into the management >>>>> 2024/05/29 23:36:12 cannot dial: dial tcp 204.13.164.252:443: connect: >>>>> connection refused >>>>> 2024/05/29 23:36:12 Event: INFO: OpenVPN Management Interface Version 5 >>>>> -- type 'help' for more info >>>>> 2024/05/29 23:36:13 Event: TCP_CONNECT >>>>> ``` >>>> >>>> Looking at the code, it seems like it is continually trying to connect. >>>> For whatever reason, the VPN is unable to connect to the end point here -- >>>> could >>>> you please cross-check that this is not a local/ISP issue for you? >>>> ( I highly suspect this ) >>>> >>>> Is the same working fine with older (in stable) version of riseup-vpn? >>>> >>>>> Here on the machine there is a tor instance running at 127.0.0.1:9050, I >>>>> am not sure if this causes any conflict between riseup-vpn and tor. I >>>>> start riseup-vpn from terminal commandline and there is no proxy related >>>>> environment variables loaded. >>>> >>>> I don't think tor has anything to do here unless it is causing some port >>>> conflict. >>>> >>>>> Thanks. >>>>> >>>>> >>>>> -- System Information: >>>>> Debian Release: 12.5 >>>>> APT prefers stable-updates >>>>> APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, >>>>> 'stable') >>>>> Architecture: amd64 (x86_64) >>>>> >>>>> Kernel: Linux 6.7.12+bpo-rt-amd64 (SMP w/4 CPU threads; PREEMPT) >>>>> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >>>>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 riseup-vpn depends on: >>>>> ii ca-certificates 20230311 >>>>> ii iproute2 6.1.0-3 >>>>> ii iptables 1.8.9-2 >>>>> ii libc6 2.36-9+deb12u7 >>>>> ii libgcc-s1 12.2.0-14 >>>>> ii libqt6core6 6.4.2+dfsg-10 >>>>> ii libqt6gui6 6.4.2+dfsg-10 >>>>> ii libqt6qml6 6.4.2+dfsg-1 >>>>> ii libqt6svg6 6.4.2-2 >>>>> ii libqt6widgets6 6.4.2+dfsg-10 >>>>> ii libstdc++6 12.2.0-14 >>>>> ii lxpolkit [polkit-1-auth-agent] 0.5.5-2+b1 >>>>> ii openvpn 2.6.3-1+deb12u2 >>>>> ii pkexec 122-3 >>>>> ii procps 2:4.0.2-3 >>>> Best, >>>> Nilesh
