neo icon indicating copy to clipboard operation
neo copied to clipboard

Release a working version of Neo CLI for macOS

Open lock9 opened this issue 2 years ago • 8 comments

Summary or problem description It's not possible to run Neo CLI using OSX. This is likely caused by changes in Apple security policies. I'm using this link to download Neo CLI: https://github.com/neo-project/neo-node/releases/tag/v3.6.2 image

Another minor issue is that the latest release can only be obtained from the archived repository. Users should be able to download neo-cli from this repository.

Do you have any solution you want to propose? Complete solution: Fix the build & release process to generate valid neo-cli executables. Partial solution: Compile the project locally and make a manual release.

The problem with the second solution is that we can't be sure that the code wasn't tampered. It's also not a permanent fix.

lock9 avatar Mar 06 '24 16:03 lock9

Fix the build & release process to generate valid neo-cli executables

What is wrong?

shargon avatar Mar 06 '24 23:03 shargon

It doesn't run. There is an error saying "This software needs to be updated. Contact the developer for more information"

lock9 avatar Mar 07 '24 02:03 lock9

should say, contact mac to find out why it says this hahaha

shargon avatar Mar 07 '24 07:03 shargon

As I got this often when running cli on MacOS. @lock9, I think we should somehow update the docs for the dev/user to manually allow this executable via System settings.

Here is the screenshot of those: Privacy   Security developer of neo-cli  Are you

This is a very normal behavior on MacOS. So what do you think about my approach @lock9 ?

kudo28 avatar Mar 10 '24 11:03 kudo28

Hello,

The problem is that it's not one alert. It's more like 20. Users must repeat the procedure almost indefinitely to be able to run it. Another issue is that this scares users. Nearly nobody will want to use software that 'may be malicious', even less when talking about a blockchain node and wallet.

Screenshot 2024-03-10 at 13 30 34

One solution to 'reduce' the issue is to build and ship neo-cli as a single file. Then, the user will have to authorize it only once.

This is a recent change made by Apple, it's likely that other teams will have to adjust their software to avoid this issue.

This was my original message on Discord:

FYI:
We will need an Apple developer account to create valid releases. Otherwise, users will face an error. 
Options:
 
- Ask users to open the security panel and allow the application to run
   - This is fine to do using Neo Go because it's just one executable. However, not possible with Neo CLI because it's shipped with multiple files (requiring users to authenticate all of them - not feasible).
- Create an Apple account that can be used by communities to generate valid releases. I recommend using an US/HK based company to create it.

lock9 avatar Mar 10 '24 16:03 lock9

it would be good to publish a single file for macos platforms @superboyiii

vang1ong7ang avatar Mar 19 '24 08:03 vang1ong7ang

it would be good to publish a single file for macos platforms @superboyiii

#3018 does just that.

cschuchardt88 avatar Mar 19 '24 08:03 cschuchardt88

Also PR #3103 for neo n4 cli will be the next release that will address all the issues.

Also any features or issues you all are more than welcome to comment at that PR.

cschuchardt88 avatar Mar 24 '24 10:03 cschuchardt88