What is the timeline for making wireguard viable for commerical VPNs?<p>"""<p>There's a few fundamental issues with wireguard that make it relatively unsuitable for commercial VPNs with many customers.<p>For a start, if you want to offer customers multiple concurrent devices, each device needs it's own key, and all keys for all customers' devices need to be loaded into kernel memory and cross checked against every packet received, which as you might imagine gets incredibly unwieldy and could savagely impact the performance of PIA servers.<p>When wireguard has the ability to hook a userspace daemon when it receives a valid-looking packet with unrecognised encryption, it'll be a lot closer to usable in commercial contexts, as the daemon could poke a database or cache to load the required keys on demand<p>"""<p><a href="https://www.reddit.com/r/PrivateInternetAccess/comments/d1blo2/wireguard_update/ezk41ix/" rel="nofollow">https://www.reddit.com/r/PrivateInternetAccess/comments/d1bl...</a>