Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Alessio Nossa <alessio.nossa+list@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: [wireguard-apple] Siri Shortcuts/Intents integration
Date: Sun, 16 Jan 2022 01:11:09 +0100	[thread overview]
Message-ID: <CAMTfdYr3YRv4MQKBhbj=Mq-QK_7nQF_DsbsB2wPLCf-idV8=ig@mail.gmail.com> (raw)

Hello
In the last month I worked on the implementation of Siri
Shortcuts/Intents integration for the WireGuard app (at the moment,
only on iOS), to automate some tasks like connecting a
tunnel, getting tunnel peers, and updating configuration at runtime. I
saw that this feature was on your TODO List too [1].

My idea is to have an interface to manage connections, to make up for
the absence of wgctrl-go [2] on iOS. I need this to dynamically update
endpoints at runtime for NAT Traversal purposes [3]; specifically, I
need peers' public keys and a way to set endpoints at runtime [4].

There are some issues due to an Apple's bug [5] that doesn't allow an
extension to update the configuration owned by its parent app. As a
workaround the update configuration action will launch the main app.

As this is my first time contributing to wireguard-apple, if you have
any advice, I'm here to hear from you.
As suggested in macOS and iOS TODO list, I’d like to have push access
to the repository (or any other way I can submit it) to contribute
with my work (I already sent an email to team at wireguard.com, but
received no response).

Kind regards,

[1] https://docs.google.com/document/d/1BnzImOF8CkungFnuRlWhnEpY2OmEHSckat62aZ6LYGY
[2] https://github.com/WireGuard/wgctrl-go
[3] https://www.jordanwhited.com/posts/wireguard-endpoint-discovery-nat-traversal/
[4] https://github.com/jwhited/wgsd/blob/master/cmd/wgsd-client/main.go
[5] https://developer.apple.com/forums/thread/96020

                 reply	other threads:[~2022-01-16 21:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAMTfdYr3YRv4MQKBhbj=Mq-QK_7nQF_DsbsB2wPLCf-idV8=ig@mail.gmail.com' \
    --to=alessio.nossa+list@gmail.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 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).