Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Ryan Whelan <rcwhelan@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: October, Paris, France - Meticulous In-person WireGuard Codebase Study Session
Date: Mon, 9 Oct 2017 20:51:18 -0400	[thread overview]
Message-ID: <CAM3m09Safbn4g7kgfrCVPtcuT19SZsyiy_R65+jDmOmKi7ygUA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9ovdYWEMkQKedvO+-4p4X5dOVARFhQ_W74sXJyvP=53Pg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

Is there any chance this could be recorded and posted to youtube or the
like?  I personally would be very interested in this knowledge, but will
not be able to attend.

On Mon, Oct 9, 2017 at 7:19 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hey folks,
>
> A few friends asked if I'd do a meticulous read through and
> explanation, in person, of every line of the relatively short
> WireGuard code base. We had done this at some point in 2015, before
> the project was made public, and it took several highly intense hours
> to study the whole thing, but was a fairly interesting time for all
> (though undoubtedly mentally exhausting to the fullest).
>
> Now they're asking me to do it again. But this time I thought I'd
> extend the session to a bit larger group.
>
> If anybody is in Paris during the next few weeks and would like to
> attend, please let me know, either on list or off list, and we'll pick
> a time and place and all meet up for several hours of intense study.
>
> Requirements are a working knowledge of C and a general idea of what
> it's like to use WireGuard. The rest of everything will be explained
> line by line in an thorough and detailed fashion. The end result is
> that all attendees will be capable of contributing to WireGuard and
> hacking on the code base. You and I will both learn a lot from
> discussing crypto and strange algorithms, and I expect it to be
> productive for everybody involved.
>
> So, if this sounds fun to anybody in town, don't hesitate to shout out.
>
> See you soon maybe,
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #2: Type: text/html, Size: 2275 bytes --]

  reply	other threads:[~2017-10-10  0:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 23:19 Jason A. Donenfeld
2017-10-10  0:51 ` Ryan Whelan [this message]
2017-10-10  1:55   ` Eric Light
2017-10-10  5:06 ` Greg KH
2017-10-11 13:52   ` Le Sandie
2017-10-11 14:10     ` Konstantin Ryabitsev
2017-10-10  6:10 ` Greg KH
2017-10-10  6:36   ` Tom Bowditch
2017-10-13 11:14     ` Manuel Schölling
2017-10-22  9:55 ` Quentin

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=CAM3m09Safbn4g7kgfrCVPtcuT19SZsyiy_R65+jDmOmKi7ygUA@mail.gmail.com \
    --to=rcwhelan@gmail.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).