Matt Layher

I've implemented the updated read-only interface and plan to do the configuration API soon!

Current state: ``` -bash-5.0# WGCTRL_INTEGRATION=yesreallydoit go test -v -run=TestIntegrationClient/get . === RUN TestIntegrationClient === RUN TestIntegrationClient/get === RUN TestIntegrationClient/get/wg0 --- PASS: TestIntegrationClient (0.00s) --- PASS: TestIntegrationClient/get (0.00s) --- SKIP: TestIntegrationClient/get/wg0...

@stv0g please do, thanks! I implemented this as an experiment and chance to learn, but never got to the configuration.

> You expose its representation only halfway: you say it's a byte array (is that important?), but don't say its length. > > If it's going to be opaque-ish, just...

I've exported KeyLen and removed ClearKey to avoid value/pointer confusion: https://github.com/mdlayher/wireguardctrl/commit/89ec2561f2658b562d135a082c8795435e09b906 Any further thoughts?

The feedback is much appreciated, thanks. I may not get to this before GopherCon, so I'll leave the issue open for tracking what we can do to remove a few...

It would seem to me that perhaps it makes sense to expose a couple of APIs here that can be composed with the existing `c.ConfigureDevice()` method. ```go package wgctrl //...

It looks like you aren't checking the error return value. Can you please provide a runnable code snippet that reproduces this?

Can you please clarify the following: - what type of device is this "arm7" machine? - which WireGuard implementation are you using on this device: kernel, wireguard-go, boringtun, other? -...

If you're building a Go program on this device, it'd be useful if you could poke around a bit and make some modifications to wgctrl-go to help me better diagnose...