External State Management about wag

[NHAS]

Hi Chris, Im going to assume you want to destroy the wag boxes aggressively so it becomes incredibly difficult for an attacker to maintain persistence on your ingress machine?

Or is this for updates/infra as code?

I'd be more than happy for this to be an addition to wag as I think it makes sense.

I am currently working on a couple things which will delay my involvement in this. Such as moving on from eBPF, Websocket challenge response, and better etcd cluster roaming.

[ChrisPortman]

Hi Chris, Im going to assume you want to destroy the wag boxes aggressively so it becomes incredibly difficult for an attacker to maintain persistence on your ingress machine?

Or is this for updates/infra as code?

Yep, both of these essentially. :) Happy to help

Such as moving on from eBPF

Side Note: Are you looking to replace eBPF?

I am currently working on a couple things which will delay my involvement in this.

I'm happy to help - let me see how my next few weeks are shaping up, might be able to have a stab at it.

[NHAS]

I am indeed looking to replace eBPF because I've realized my solution is much more complicated than it needs to be and it can all be squashed into just pure go.

There are also a bunch of other thing its may enable, like better cluster roaming as then I may fork wireguard-go and add in the ability to set keypairs for different peers. Which would mean that even under aggressive loadbalancing users would never face downtime

[NHAS]

Im more than happy for anyone (yourself included) to open pull requests! With the obvious caveat that I might be quite picky with what people implement.