From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Package Request: nordvpn
Date: Mon, 24 Jun 2019 20:43:27 +0200 [thread overview]
Message-ID: <20190624184327.aInjJDxVeRJfZkKQO0JvVI3azKyrH0Wxi4AXX_E8m7Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11356@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
New comment by kernle32dll on void-packages repository
https://github.com/void-linux/void-packages/issues/11356#issuecomment-505131220
Comment:
Got it all running after some tinkering. The daemon `nordvpnd` runs fine as a simple runit service without any frills.
However, something that worries me is that the nordvpn deb file re-distributes its own (I presume) statically built `openvpn`. For testing purposes I linked `/usr/bin/openvpn` to `/var/lib/nordvpn/openvpn`, and it seems to run fine. However, I was unable to find any licensing information that would give me clues about whether or not it would be OK to re-distribute nordvpn this way (without its own openvpn build).
next parent reply other threads:[~2019-06-24 18:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11356@inbox.vuxu.org>
2019-06-24 18:43 ` voidlinux-github [this message]
2020-03-22 20:38 ` Ingvix
2020-03-22 20:38 ` Ingvix
2020-04-14 8:21 ` ovinsnes
2020-04-14 8:24 ` Ingvix
2020-04-14 11:16 ` ovinsnes
2020-04-14 11:38 ` flexibeast
2020-04-14 11:41 ` flexibeast
2020-04-14 11:46 ` flexibeast
2020-04-14 12:20 ` Ingvix
2020-04-17 22:10 ` kernle32dll
2020-04-18 9:39 ` kernle32dll
2020-10-04 0:42 ` the-maldridge
2022-04-15 0:52 ` github-actions
2022-07-29 19:39 [ISSUE] Package request: NordVPN BT-Justice
2022-07-29 19:43 ` BT-Justice
2022-07-29 19:58 ` classabbyamp
2022-07-29 20:05 ` BT-Justice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190624184327.aInjJDxVeRJfZkKQO0JvVI3azKyrH0Wxi4AXX_E8m7Q@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).