wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Lee Yates <rainmakerraw@icloud.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for iOS - TestFlight
Date: Mon, 05 Nov 2018 22:53:19 +0000	[thread overview]
Message-ID: <2FFC5AC1-8BA3-4ACB-97E6-04990AA2DA8B@icloud.com> (raw)
In-Reply-To: <CAHmME9p5bjmP8qSapvf1vmiMAk3BAkONjwXev3O_QtGYM=k3QQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2668 bytes --]

This is great news! Well done Jason and Roopesh.

I’m no app coder, but I can at least give my feedback for what that’s worth. It imported my conf via QR and connected without issues, so far. It’ll be great to see VPN-on-Demand added (eg phone restarts, dead batteries, network switches(?) etc). I’ve also been testing the TunSafe iOS app, which does have VPNoD but is bugging out with UDP writes atm. No doubt soon enough we’ll have at least two good open source apps to choose from. It’s great to have such choice and flexibility when working with my favourite VPN protocol. Keep up the great work everyone, and thanks for what you do.


> On 5 Nov 2018, at 21:27, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> 
> Hey folks,
> 
> For the last few weeks, Roopesh and I have been hard at work on the
> WireGuard for iOS app. Today we're happy to share a
> likely-buggy-and-broken TestFlight that you can run on your phone:
> <https://testflight.apple.com/join/63I19SDT>. As usual, use at your
> own risk, especially since it's alpha quality.
> 
> Please let us know about any bugs as you find them -- you can send
> them to me or to team@wireguard.com. Our current TODO list lives here
> [1], linked via the main project TODO list [2], and if you're an iOS
> person and want to contribute code, we'd be happy to have you on
> board.
> 
> The app costs $3.99 and requires an email address to sign up; we
> manage all your tunnels for you in the cloud. JUST KIDDING! Like the
> rest of WireGuard, the iOS app is free and open source [3]. I make
> this rather tasteless joke, because of the rather surprising
> quantities of people encouraging me to do the iOS stuff as proprietary
> paid software, because "apple users will pay" or because "open source
> is cool, but iphone folks don't care about it so you can get away with
> charging" or because "none of the other vpn players are doing open
> source mobile implementations" or even because "apple is more likely
> to accept paid software into its app store" and so on and so forth.
> But, as usual, I much prefer for this to be a community project than a
> closed one, and so like everything else, it's FLOSS.
> 
> Enjoy! And do let us know about the bugs as you run into them. I'm
> sure there are plenty.
> 
> Regards,
> Jason
> 
> [1] https://docs.google.com/document/d/1BnzImOF8CkungFnuRlWhnEpY2OmEHSckat62aZ6LYGY
> [2] https://www.wireguard.com/todo/
> [3] https://git.zx2c4.com/wireguard-ios/
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


[-- Attachment #1.2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2018-11-05 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 21:27 WireGuard for iOS - TestFlight Jason A. Donenfeld
2018-11-05 21:44 ` Bruno Wolff III
2018-11-05 23:20   ` Jason A. Donenfeld
2018-11-05 22:53 ` Lee Yates [this message]
2018-11-05 23:49 ` nnet
2018-11-06  7:04 ` Ryan Walklin
     [not found] ` <2036724358.1451767.1541469968454@mail.yahoo.com>
2018-11-06 16:15   ` Jose Marinez
2018-12-20  1:04 ` WireGuard for iOS - now in the App Store Jason A. Donenfeld

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=2FFC5AC1-8BA3-4ACB-97E6-04990AA2DA8B@icloud.com \
    --to=rainmakerraw@icloud.com \
    --cc=Jason@zx2c4.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).