First! 😄 hah

@User trying to track your posts from the development page. It sounds like there's a few issues with packaging the client for Mac that we need to take care of.

#1 sounds like the location of the netclient is an issue, and putting it in /usr/bin would help. Coincidentally, we have this same issue on fedora/rhel/centos right now due to selinux. Sounds like in 0.9.1 we can take care of both by placing the binary in usr/bin and executing from there.

#2 sounds like the package needs to be notarized. I'm not familiar with the process for Mac but we're happy to work with you on that if it's something we can do

it needs to be signed by apple to make it "valid"

i think you need a developer account for that

thanks @User for creating this channel. I'm super happy that you are interested in making the Mac stuff work better. The basic issue is that currently you need root to do stuff, but Apple doesn't want anyone or anything to have root- so they lock down a bunch of stuff. I think it's ultimately good but currently a pain in the @ss. If you can get access to a Mac, I'll pay for your US$99 developer license. I've already worked out how to make the binary into a .app and the .app into an installer, (I think) we just need to attach the app security requirements to the installer and send it to Apple for notarisation. I do expect there will be other issues but it looks possible right now. The builds can be automated- so once done, it's not a lot of extra work to push it out. I'll summarise what I know here

Creating the .app Need to sign the binary first I used an app called 'macapp.go' to package it up, put the icon and binary into a folder called build_folder and execute

go run macapp.go -assets build_folder -bin netclient -icon ./icon.png -identifier com.servicemax.netclient -name "netclient" -o ~/Desktop

and your app will be on the desktop

Creating the installer .pkg I used munkipkg for this - there's a run through here- https://www.elliotjordan.com/posts/munkipkg-01-intro/ Munkipkg will create the folder structure for you, you add the app and the supporting files, then execute

munkipkg /Users/Shared/DeploymentTools/netmaker-munkipkg/netmaker

That .pkg then has to be signed, but this can be done as part of the munkipkg command, I just haven't figured that bit out.

What we are missing We need to specify some security entitlements inside the .pkg so that Apple will notarise the package and it will pass Gatekeeper and actually run. Best example I've found is here- https://stackoverflow.com/questions/67367102/electron-forge-osx-sign-app-result-in-binary-is-improperly-signed There's some background info about the process here- https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/ But my poor little brain is not coping with all this right now!

@User he already has access to a mac, I only built the netclient last few times because he was working remote. 🙂

thanks @User what is the build environment please? This is something I know very little about, but netclient seems to be made in Go, looks like xcode doesn't support go (much? at all?). I might be able to figure out an easy process if I know all the things...

eh.. @User helped me with that, I'm in no means a macos coder 🙂 I only pull the github repo and do go netclient in the correct folder lol

ok here's the doc about building a Mac app and installer. It's not fully tested and there is bits missing but it's close- https://servicemax.com.au/tips/signing-and-notarising-a-mac-binary-written-in-go/

and a willingness to spend so much time in front of a computer that your spouse forgets your name… I like that one hahaha

MAC OS Mojave says: unsupported OS Terminal: curl .......... uname says Darwin not darwin netclient-install.sh only looking for darwin not Darwin.

what does mojave say on uname -a?

As a stated: Marcuss-iMac-5:~ marcus$ uname -a Darwin Marcuss-iMac-5.fritz.box 18.7.0 Darwin Kernel Version 18.7.0: Mon May 3 20:41:19 PDT 2021; root:xnu-4903.278.68~1/RELEASE_X86_64 x86_64 Marcuss-iMac-5:~ marcus$ uname Darwin

right..

why always use uppercase or lowercase if you can also change it from one distro to another lol

@User merged your PR for mojave issue

How should Netclient be installed on Mac OS? Step by Step. Maybe i am doing someting wrong here?

same as linux, you should just run the install script from terminal

@User - right now, there's a bunch of things that need to be done to make it work on a Mac. If you're on Mojave you could sign it with a developer ID and it would probably work. Might also require chmod +x as root. On Catalina and above there's a bunch of other stuff required.

Hi @User - I've now got the installer working properly, but can't connect a client to the Netmaker network. Here is the error- > 2021/12/14 20:08:27 exec: "wg": executable file not found in $PATH > 2021/12/14 20:08:27 WireGuard not installed. Please install WireGuard (wireguard-tools) and try again. Tried it on a couple of machines, but this error is consistent. Wireguard is installed on both machines, so this could be because we are putting netclient in /usr/local Or maybe it netclient is looking in the wrong place for wireguard-tools?

as long as it's getting path, it shouldn't be looking anywhere specific, my wireguard tools are in my home brew directory

@User I believe the issue here is we need wireguard installed from brew, and I'm guessing you have wireguard installed from the app store?

One thing we've considered is having a version of the netclient with wireguard-go embedded into it, would that work for your use case?

I think that would be more beneficial for everyone, not too many casual home brew users out there.

Plus the pre-req of needing brew is pretty massive with the xcode hooks