From: Derrick Lyndon Pallas <derrick@pallas.us>
To: wireguard@lists.zx2c4.com
Subject: Re: wg-lla
Date: Wed, 5 Aug 2020 18:17:13 -0700 [thread overview]
Message-ID: <2e14d61e-07ac-ac6c-d6a0-30aa250abae4@pallas.us> (raw)
In-Reply-To: <CAMaqUZ2UxEC+Fz4a=dp7R=6Ca=+TRH_u1cqhEEH0q1PA6hLvBg@mail.gmail.com>
Thanks for updating!
FYI, I just added this LLA algorithm to the PublicKey class in [1] with
three caveats:
* it allows for injection into an arbitrary IPv6 or IPv4 address space
(default is the LLA/10 that wg-lla uses)
* it fails if the generated address is the network address or
broadcast address of the provided address space
* it allows for an optional blake2b key, to mix the addresses if
desired (default is no secret, which produces the same addresses as wg-lla)
~Derrick
[1] https://github.com/ArgosyLabs/wgnlpy/
On 8/1/20 9:31 PM, Reid Rankin wrote:
> A while ago, I included a link to a Gist containing `wg-lla.sh`, a
> utility for calculating and assigning IPv6 Link-Local Addresses to
> WireGuard peers based on a hash of their public key, which was based
> on a shell-script implementation of Blake2s. At the time it was
> intended as a proof-of-concept sort of thing, but I've had some
> interested parties contact me about using it -- since I neglected to
> stick on a license.
>
> So I've rectified that error, and promoted it to a proper repo. Now
> people can hopefully find it, as well as raise issues and make PRs.
> Hope it's useful!
>
> https://github.com/reidrankin/wg-lla
>
> --Reid
>
prev parent reply other threads:[~2020-08-06 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 4:31 wg-lla Reid Rankin
2020-08-06 1:17 ` Derrick Lyndon Pallas [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=2e14d61e-07ac-ac6c-d6a0-30aa250abae4@pallas.us \
--to=derrick@pallas.us \
--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).