From: Jayakumar S <jayakumar82.s@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard Windows Implementation
Date: Wed, 8 Apr 2020 16:40:29 -0400 [thread overview]
Message-ID: <CAECTAb_TW53o9Xb=F+gkamVH2aqG1iQKCiQkiO0JjTtVEE=isA@mail.gmail.com> (raw)
Hi Guys,
Thank you so much for explaining the internals of Wireguard
implementation in Linux kernel. The sequence explained in the slide
(page 11) helps a lot to understand the flow in the following
document.
https://www.wireguard.com/talks/fosdem2017-slides.pdf
Likewise, do you have any document for Windows implementation. I know
there will be a lot of differences between Windows & Linux
implementation. By any chance if you have CryptoRouting flow in
Windows it could be very useful. Basically, I want to understand the
flow between user space module, NDIS miniport driver.
Thanks,
Jay
reply other threads:[~2020-04-14 8:13 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='CAECTAb_TW53o9Xb=F+gkamVH2aqG1iQKCiQkiO0JjTtVEE=isA@mail.gmail.com' \
--to=jayakumar82.s@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).