3 ms·
Í think their point was that Wireguard has no physical hardware, so it’s strange as a software project they’d be forced to go through verification for a hardwar
by VertanaNinjai 7mo ago
Í think their point was that Wireguard has no physical hardware, so it’s strange as a software project they’d be forced to go through verification for a hardware program.
- nine_k 7mo agoBecause it's a kernel driver anyway?
- anakaine 7mo agoThen the program should have been named the kernel level driver verification program.
- literalAardvark 7mo agoMate this is Microsoft. We're lucky it's not called Azure Copilot Verification Program (New)
- UqWBcuFx6NV4r 7mo agoOkay. 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.
- anakaine 7mo agoThose 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.
- olyjohn 7mo agoIt's a virtual network interface. So it's not really hardware, but the computer treats it like it is.