From: Jose Marinez <jedi_papi@yahoo.com>
To: Maximilian Eschenbacher <maximilian+wireguard@eschenbacher.email>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard on android w/o kernel module
Date: Sat, 2 Jun 2018 21:43:26 +0000 (UTC) [thread overview]
Message-ID: <1311152671.8205402.1527975806101@mail.yahoo.com> (raw)
In-Reply-To: <20180601165401.olea7a7gljb4zwtx@kajt.de>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Pardon me, as I just sent a related message without reading this one first. The fact remains, there should be a better way to handle and prevent this. Perhaps, at a minimum and in the interim, to suggest investigating the installation of another VPN client settings right in the error message.
Thanks,Jose
On Friday, June 1, 2018, 12:54 PM, Maximilian Eschenbacher <maximilian+wireguard@eschenbacher.email> wrote:
Hey Jason,
thanks for the quick response.
On 01/06/2018 18:42:41, Jason A. Donenfeld wrote:
>You can investigate (b) by fishing around in the system VPN settings
>and seeing what's there, possibly removing authorization for those.
>Afterwards, close the application, reopen it, and it should prompt you
>to accept permissions.
This was exactly what had happened.
Best regards
Max
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: Type: text/html, Size: 2078 bytes --]
next prev parent reply other threads:[~2018-06-02 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 16:38 Maximilian Eschenbacher
2018-06-01 16:42 ` Jason A. Donenfeld
2018-06-01 16:54 ` Maximilian Eschenbacher
2018-06-02 21:43 ` Jose Marinez [this message]
2018-06-02 21:49 ` Jason A. Donenfeld
2018-06-02 22:02 ` Jose Marinez
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=1311152671.8205402.1527975806101@mail.yahoo.com \
--to=jedi_papi@yahoo.com \
--cc=Jason@zx2c4.com \
--cc=maximilian+wireguard@eschenbacher.email \
--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).