From: Tim Sedlmeyer <tim@sedlmeyer.us>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <WireGuard@lists.zx2c4.com>
Subject: Re: Removing pre-shared key from peer using wg set fails
Date: Thu, 23 Nov 2017 02:17:32 +0000 [thread overview]
Message-ID: <CAK_h9uF_miSZs=sJ4b4Dx37Ukd-sO8p_cHzJVuDBN9f9waJZvQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9r=H0Kp_3HYvxB62c3-LcMDKnYaTt-nn7b93JToWg91mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Jason,
That fixed it.
Thanks,
Tim
On Wed, Nov 22, 2017 at 7:20 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Hi Tim,
>
> Thanks for letting me know. This is a tools regression from
> 0.0.20171111, which I just fixed, based on your report:
>
>
> https://git.zx2c4.com/WireGuard/patch/?id=7153081da70006a8723474580543bd3223d1baf4
>
> Let me know if this fixes the issue. It will be included in the next
> snapshot.
>
> Regards,
> Jason
>
[-- Attachment #2: Type: text/html, Size: 914 bytes --]
prev parent reply other threads:[~2017-11-23 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 23:53 Tim Sedlmeyer
2017-11-23 0:20 ` Jason A. Donenfeld
2017-11-23 2:17 ` Tim Sedlmeyer [this message]
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='CAK_h9uF_miSZs=sJ4b4Dx37Ukd-sO8p_cHzJVuDBN9f9waJZvQ@mail.gmail.com' \
--to=tim@sedlmeyer.us \
--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).