Use NetworkExtension API to on macOS rather than direct tun interface about lokinet HOT 3 CLOSED

one associated worry i have is that this will add a hard requirement on having code signed binaries on apple platforms, which makes compiling it harder.

from lokinet.

I think that fear is a bit misplaced.

The requirement always exists for iOS, no matter what, but code signing certificates are readily available. The project can even distribute outside the app store with enterprise distribution channels (the iOS app can be a build artefact on a repo, even, and users can install from their browser). This requires those compiling to have access to a code signing certificate, however, which can cost $99 per year for some.

For macOS, using the NetworkExtension API means in a system configured following security best-practices, code signing will be required, however, there is nothing stopping users from singing with a self-signed certificate they have installed to their own machine.

TL;DR self-signed certs can be used for macOS, this is a non-issue in practice

@majestrate @neuroscr

from lokinet.

fixed in recent dev branch. just need to wire it up to a gui.

from lokinet.