Ok, thanks for the update.

There is no rush from ym side. I was more interested in trying this out.
I am working in the Medical Industry where crypto is pretty important and
so am looking to run this between mobile devices and the servers.
I run golang on mobiles now.

Is there any impediment to running n Android and IOS ?

I can also try to help with the code. I worked in security but not really
crypto.

Regards

Joe (Berlin)

On Wed, Mar 29, 2017 at 7:49 AM James Tucker <jftucker@gmail.com> wrote:

> I have more in a local repo, but it's very disorganized as I'm taking a
> more "port" approach with the internal structures right now. After some
> discussions with Jason it seemed I wasn't keeping up enough with some of
> the important internal behaviors. Once this port approach is a little
> further along I'll be able to carve out meaningful individual pieces with
> tests for submitting.
>
> If you wanted something sooner, cobbling together the uapi code I have in
> wireguard-go, with the implementation stuff in go-wireguard would probably
> work relatively more quickly than I'll finish off, but the end goal I have
> is a little cleaner than what that would be.
>
> I don't suspect I have a ton of work to do, but mostly it's finding the
> time to sit down and make decent chunks of progress, as my day to day is
> quite full. If you or others are ready to lay down some time, I'd be more
> than willing to push up pieces earlier and/or coordinate.
>
> If I don't catch up with the ML soon enough, feel free to highlight me in
> irc and/or reach out to me over other mediums. I don't keep up with this
> email too well when I'm this busy.
>
> On Fri, Mar 17, 2017 at 6:53 AM, Joe Blue <joeblew99@gmail.com> wrote:
>
> Thanks.
>
> Seems this is the git endpojnt: https://git.zx2c4.com/wireguard-go/about/
>
> In the toDO there is a fair bit there. Is it ready for me to be able to
> work on anything or still very bare bones ?
>
>
>
>
>
> On Fri, Mar 17, 2017 at 1:34 PM Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
>
> Hello Joe,
>
> I defer to James Tucker, CCd, to describe the status of his implementation.
>
> Regards,
> Jason
>
>
>