Because it's a kernel driver anyway?
replyThen the program should have been named the kernel level driver verification program.
replyOkay. So they can call it the “hardware and WireGuard” program for all I care. The reality is that MS requires this sort of approval / verification process for whatever WireGuard is doing. In true HN fashion everyone loves getting distracted by utter meaningless semantics.
replyThose meaningless semantics are part of how this got missed in the first place, and why it caused such an issue. Microsoft is a large company, and a poorly named program created requirements that were missed.
replyIt's a virtual network interface. So it's not really hardware, but the computer treats it like it is.
reply