Page MenuHomeSolus

AirVPN Client
Closed, WontfixPublic

Description

Name: AirVPN Client

Website: https://airvpn.org/
Linux Version available : https://airvpn.org/linux/

Open Source: https://github.com/AirVPN/airvpn-client

frendznet triaged this task as High priority.
JoshStrobl lowered the priority of this task from High to Normal.Sep 6 2016, 11:05 PM
JoshStrobl removed ikey as the assignee of this task.
JoshStrobl added subscribers: ikey, JoshStrobl.

Don't change the default statuses of Tasks or change the assignee.

JoshStrobl renamed this task from AirVPN Client Package Request to AirVPN Client.Sep 6 2016, 11:07 PM
JoshStrobl updated the task description. (Show Details)
JoshStrobl added a project: Package Requests.
JoshStrobl removed a subscriber: ikey.

Don't change the default statuses of Tasks or change the assignee.

ok :-)

DataDrake closed this task as Invalid.Sep 17 2016, 5:59 PM
DataDrake added a subscriber: DataDrake.

No valid release tarballs for source. Not going to package this.

frendznet reopened this task as Open.EditedSep 28 2016, 12:56 AM

tarballs??

so how can i access my VPN without the client?
Sorry but newbie here on Linux

DataDrake closed this task as Wontfix.Sep 28 2016, 12:58 AM
DataDrake claimed this task.

Without a valid release tarball or zip file for the source, this will not be packaged. It's not enough for the source to just be on git. You are welcome to download their pre-built portable version and use that.

DataDrake changed the edit policy from "All Users" to "Triage Team (Project)".Sep 28 2016, 12:58 AM
ikey added a comment.Sep 28 2016, 6:49 PM

From AirVPN forums:

This is a hilarious statement. I'm not sure I would like to use a distribution from such a developer, though. Who knows when something
else is going to be broken or will require patching. Many drivers and other sources are on git and it's seems like not enough for him to get things done.

They only have to create a git tag and we can take it from there. This is such a fundamental part of software development and release practices.
You create an immutable point in history, and we package that specific, tested, version. We can ship git versions of packages, and in quite
a few places we do, but this demonstrated disdain for versioning and proper releases makes it, at present, very unattractive.

Once they throw a git tag up on GitHub (all of 2 commands in a terminal) we can reassess this.

Any chance of looking onto this again?

baimafeima reopened this task as Open.Feb 1 2017, 8:24 PM

They have finally released versioned tarballs. I have re-opened this for re-evaluation.
Discussion: https://github.com/AirVPN/airvpn-client/issues/44
https://github.com/AirVPN/airvpn-client/archive/v2.11.15.tar.gz

ikey added a comment.Feb 1 2017, 10:57 PM

Yep, can go in now

ikey added a comment.Feb 1 2017, 11:12 PM

Ugh I might redact that statement?

Build system tells you it failed, and then it succeeds. Documentation for paths is wrong, build system generates a tarball,
which is pretty useless. Extract the tarball, we find a handful of useful files (We won't be using a bundled openvpn binary,
that's a security hole waiting to happen)

 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  tar xf ../repository/files/eddie-cli_2.11.15_linux_x64_mono.tar.gz 
 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  ls
eddie-cli_2.11.15_linux_x64_mono
 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  tree
.
└── eddie-cli_2.11.15_linux_x64_mono
    ├── Eddie-CLI.exe
    ├── Lib.Common.dll
    ├── Lib.Core.dll
    ├── openvpn
    ├── Platforms.Linux.dll
    ├── stunnel
    └── update-resolv-conf

1 directory, 7 files

So yes, it's "doable". Fact of the matter is, the update-resolv.conf script falls into the evil category. As does bundling openvpn, but I can
understand that from a cross platform perspective. Now, given that "Eddie" is a cross-platform OpenVPN wrapper (in essence) - is there any
reason you can't just use Network Manager OpenVPN directly for this? As this will ensure that you use our openvpn binary, and that NM is
able to properly set up gateways and manage /etc/resolv.conf itself (as it currently does)

DataDrake removed DataDrake as the assignee of this task.Feb 18 2017, 10:13 PM

No update yet to when the client will be available for Solus?

is there any reason you can't just use Network Manager OpenVPN directly for this? As this will ensure that you use our openvpn binary, and that NM is
able to properly set up gateways and manage /etc/resolv.conf itself (as it currently does)

Just came across this package request since I wanted to install eddie also.

A couple of reasons for not using Network Manager. The first is that it is much easier to switch between many servers rather than importing one by one in NM. The other is that the GUI has a network lock feature, which prevents any non-VPN traffic therefore minimising risk of leaking address. As far as I'm aware, this feature is not implemented in NM. Not a technical person on how vpns work, so personally would like to use the GUI that has the network lock feature than trying to figure out the command line equivalent.

baimafeima rescinded a token.
baimafeima awarded a token.
JoshStrobl closed this task as Wontfix.Aug 11 2018, 1:32 PM
JoshStrobl claimed this task.

It's been nearly a month since we've marked this as Needs Maintainer and nearly 6 since it's been accepted, with nobody stepping up to provide an accepted patch. Closing as WONTFIX.