From: Matt Layher <mdlayher@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Andrew Roth <andrew@andrewjroth.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Python Wrapper for wireguard-tools
Date: Mon, 31 Aug 2020 16:40:58 -0400 [thread overview]
Message-ID: <00e010bb-33c8-5885-e7ff-7e6aa8ba1dc1@gmail.com> (raw)
In-Reply-To: <CAHmME9qoWSURAqdQJuOdo9xCBgrtENNOGgf_o1uRep66xRWzJw@mail.gmail.com>
Hi all,
Apologies for the delay! I meant to reply much sooner but lost track.
I would also encourage you to use the native interfaces as much as
possible, rather than binding to C or shelling out to wg(8). If you have
any questions about decisions I made in wgctrl-go, I'd be happy to share
my thoughts.
- Matt
On 8/22/20 3:05 PM, Jason A. Donenfeld wrote:
> Hey Andrew,
>
> The most complete "library" is actually the wgctrl-go one from Matt
> (CC'd). It's complete because it supports all the same interfaces as
> wg(8) -- Linux Netlink, OpenBSD IOCTL, and x-platform UAPI. The
> embeddable-wg-library is just for Linux Netlink, but I should maybe
> refactor that to be more modular. And as you pointed out, the wgnlpy
> stuff is Netlink also.
>
> If you wanted to start a new cross-platform library, and essentially
> "clone" Matt's Go library into a pure Python one, I'd certainly
> welcome that effort and would be happy to help.
>
> Jason
next prev parent reply other threads:[~2020-08-31 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:04 Python Wrapper for wireguard-tools Andrew Roth
2020-08-22 19:05 ` Jason A. Donenfeld
2020-08-22 21:14 ` Derrick Lyndon Pallas
2020-08-31 20:40 ` Matt Layher [this message]
2020-08-24 14:37 ` Arti Zirk
2020-08-24 18:57 ` Ryan Whelan
[not found] ` <CAKmhVko10JYo__SfNGujkeVV_YCPVLtBkLzcXoMfo7X3qjD5pA@mail.gmail.com>
2020-08-24 19:38 ` Mo Balaa
2020-08-27 8:34 ` Jason A. Donenfeld
2020-08-27 8:59 ` Mo Balaa
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=00e010bb-33c8-5885-e7ff-7e6aa8ba1dc1@gmail.com \
--to=mdlayher@gmail.com \
--cc=Jason@zx2c4.com \
--cc=andrew@andrewjroth.com \
--cc=wireguard@lists.zx2c4.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.