Re: NetworkManager Plugin

[Maximilian Moser <e1326252@student.tuwien.ac.at>]

Hey Jason,


>> I actually just wanted to get this thesis over with and thought, why not
>> post the result to the mailing list
>> I'll probably focus more on the written part of the
>> thesis, so fixing the issues will probably have to wait a while on my part.
> I'm certainly not interested in "throw it over the fence" coding. I'm
> happy to work with you on "the acceptance and the possible prospect of
> this thing getting packaged for distros," as you wrote, but only if
> you're actually committed to maintaining it. It sounds to me like this
> is something in your mind that is "over with"? That's disapointing.

Oh sorry, that wasn't my intention to say. What I meant is that I wanted 
to get a working prototype ASAP, and if nobody is interested in it 
anymore, that's that.

However, this does not seem to be the case and I'll be glad to continue 
development on it. :)


Max


On 15/02/18 15:07, Jason A. Donenfeld wrote:
> Hi Max,
>
> On Thu, Feb 15, 2018 at 1:34 AM, Maximilian Moser
> <e1326252@student.tuwien.ac.at> wrote:
>> I actually just wanted to get this thesis over with and thought, why not
>> post the result to the mailing list
>> I'll probably focus more on the written part of the
>> thesis, so fixing the issues will probably have to wait a while on my part.
> I'm certainly not interested in "throw it over the fence" coding. I'm
> happy to work with you on "the acceptance and the possible prospect of
> this thing getting packaged for distros," as you wrote, but only if
> you're actually committed to maintaining it. It sounds to me like this
> is something in your mind that is "over with"? That's disapointing.
>
>> Regarding the issues... About some of them, I did know in one way or the
>> other.
>> So I'm somewhat excited about the acceptance and the possible prospect of
>> this thing getting packaged for distros :D
> As I wrote earlier, this is going to require a lot of work to actually
> bring to fruition. The first priority should be entirely dispensing
> with the use of wg-quick. In order to aid these efforts, I spent some
> time writing a mini single-file-c library that you can drop into your
> project as a means for talking to the kernel and configuring devices
> directly:
>
> https://git.zx2c4.com/WireGuard/tree/contrib/examples/embeddable-wg-library/README
>
> Should be pretty straight-forward to integrate. You'll basically only
> need to use the "wg_set_device" function, and perhaps the
> "wg_key_from_base64" function too.
>
> Jason