Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release a working version of Neo CLI for macOS #3176

Open
lock9 opened this issue Mar 6, 2024 · 8 comments
Open

Release a working version of Neo CLI for macOS #3176

lock9 opened this issue Mar 6, 2024 · 8 comments
Labels
Discussion Initial issue state - proposed but not yet accepted

Comments

@lock9
Copy link
Contributor

lock9 commented Mar 6, 2024

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 lock9 added the Discussion Initial issue state - proposed but not yet accepted label Mar 6, 2024
@shargon
Copy link
Member

shargon commented Mar 6, 2024

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

What is wrong?

@lock9
Copy link
Contributor Author

lock9 commented Mar 7, 2024

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

@shargon
Copy link
Member

shargon commented Mar 7, 2024

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

@kudo28
Copy link

kudo28 commented Mar 10, 2024

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 ?

@lock9
Copy link
Contributor Author

lock9 commented Mar 10, 2024

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.

@vang1ong7ang
Copy link
Contributor

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

@cschuchardt88
Copy link
Member

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

#3018 does just that.

@cschuchardt88
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants