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

'IPFS Desktop' can't be opened because Apple cannot check it for malicious software #1211

Closed
brennanfife opened this issue Oct 23, 2019 · 10 comments
Labels
area/macos MacOS help wanted Seeking public contribution on this issue status/blocked Unable to be worked further until needs are met

Comments

@brennanfife
Copy link

Reinstalled Brave with the IPFS Chrome extension and the IPFS Companion Desktop application this morning. Opened it, but only get this warning with the following description: 'this software needs to be updated. Contact the developer for more information.'

Currently running macOS Catalina 10.15

@pcowgill
Copy link

FYI this still is an issue for fresh installs

@andrew
Copy link
Contributor

andrew commented Jan 21, 2020

I ran into the same error this morning:

Screenshot 2020-01-21 at 11 06 05

It can be fixed by IPFS devs "Notarizing" the app with Apple before releasing it: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution

@lidel
Copy link
Member

lidel commented Jan 21, 2020

Reopening. We need someone with Mac for this:

Notarization requires Xcode 10 or later.
Building a new app for notarization requires macOS 10.13.6 or later.

Seems that the process can be automated via CI:

If you use an automated build system, you can integrate the notarization process into your existing build scripts. The altool and stapler command-line tools (included with Xcode) allow you to upload your software to the Apple notary service, and to staple the resulting ticket to your executable.

Ref.

@lidel lidel reopened this Jan 21, 2020
@lidel lidel added help wanted Seeking public contribution on this issue area/macos MacOS release labels Jan 21, 2020
@hacdias
Copy link
Member

hacdias commented Jan 21, 2020

lidel added a commit that referenced this issue Feb 3, 2020
- ensure correct webui is used (clean before each build)
- switch to latest electron and electron-builder
  (CI uses npm ci due to package-lock.json)
  - latest electron-builder includes fixes needed for notariztion of mac artifact
    (#1211)
- switch to future-proof multiaddr-to-uri

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
lidel added a commit that referenced this issue Feb 3, 2020
* chore: dependency updates

- ensure correct webui is used (clean before each build)
- switch to latest electron and electron-builder
  (CI uses npm ci due to package-lock.json)
  - latest electron-builder includes fixes needed for notariztion of mac artifact
    (#1211)
- switch to future-proof multiaddr-to-uri
- fix CI: cache downloaded electron and electron-builder artifacts
@lidel
Copy link
Member

lidel commented Feb 3, 2020

No Mac at hands, but I moved the needle a bit:

@lidel
Copy link
Member

lidel commented Feb 4, 2020

For now, I think we could try to manually notarize v0.10.3:

  • IIUC we need someone with Xcode and AppleID
    • I am not sure if it needs to be the same ID as one used for signing:
      signing         file=dist/mac/IPFS Desktop.app identityName=Developer ID Application: Protocol Labs, Inc. (7Y229E2YRL) identityHash=C297E064280322D72444C869E7FC0F60B14E934E provisioningProfile=none
      
      @olizilla do you remember who owns keys used at Travis by any chance?
  • Try executing step (2) described at Notarize Your Preexisting Software, but note that:

    Alternatively, you can put apps, kernel extensions, and other software in a container, like a disk image, and notarize the container. The notary service accepts disk images (UDIF format), signed flat installer packages, and ZIP archives.

@lidel lidel mentioned this issue Feb 4, 2020
22 tasks
@lidel lidel added the status/blocked Unable to be worked further until needs are met label Feb 4, 2020
@lidel lidel mentioned this issue Feb 17, 2020
@lidel lidel pinned this issue Feb 27, 2020
lidel added a commit that referenced this issue Feb 27, 2020
This runs electron-notarize as additional step on darvin runtime, loosly following
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

This is work in progress (I have no Mac, so we need to use CI)

Context:
#1211

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
lidel added a commit that referenced this issue Feb 27, 2020
This runs electron-notarize as additional step on darvin runtime, loosly following
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

This is work in progress (I have no Mac, so we need to use CI)

Context:
#1211

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
lidel added a commit that referenced this issue Mar 9, 2020
This adds scripts that run electron-notarize
as additional manual or build steps on darvin runtime, loosly following
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

Context:
#1211

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
lidel added a commit that referenced this issue Mar 10, 2020
This adds scripts that run electron-notarize
as additional manual or build steps on darvin runtime, loosly following
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

Context:
#1211

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
lidel added a commit that referenced this issue Mar 10, 2020
* chore: macOS notarizing

This adds scripts that run electron-notarize
as additional manual or build steps on darvin runtime, loosly following
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

Context:
#1211

entitlements should enable us to pass process with go-ipfs binary
electron-userland/electron-builder#3940 (comment)

notarize-cli.js uses electron-notarize-dmg,
works like electron-notarize but supports DMG without
stapling (which is what we want for now)

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
@lidel
Copy link
Member

lidel commented Mar 12, 2020

Thanks to help from @olizilla and @autonome this is now fixed in 0.10.4 \o/

0.10.3

Screenshot 2020-03-12 at 14 18 07

0.10.4

Screenshot 2020-03-12 at 14 18 30

Details: #1365

@lidel lidel closed this as completed Mar 12, 2020
@lidel lidel unpinned this issue Mar 12, 2020
@hacdias hacdias mentioned this issue Apr 27, 2020
22 tasks
@slhodak
Copy link

slhodak commented Mar 21, 2021

I get the "Is an app downloaded from the internet" warning, and click open, and Activity Monitor says the following processes are running, but there is no ipfs window, nor a dot next to the icon in the dock.
ipfs
IPFS Desktop
IPFS Desktop Helper (Renderer)
IPFS Desktop Helper (GPU)

IPFS Desktop Version 0.14.0

System

Catalina 10.15.7

I do have two graphics cards (one additional) but am not sure if that's related:
NVIDIA GeForce GT 650M 512 MB
Intel HD Graphics 4000 1536 MB

And I only have 35GB of free disk space--would that be an issue?

@slhodak
Copy link

slhodak commented Mar 21, 2021

After trying it out, I think I should mention here that I've run IPFS from the command line and it seems to work fine, including the local browser UI.

@anthraxblast
Copy link

anthraxblast commented Jul 6, 2021

I'm getting the same issue as slhodak - no matter what I do, I cannot get IPFS desktop (v 0.15.0) to work on Mac. MacBook Air (13-inch, Early 2015), 1.6 GHz Dual-Core Intel Core i5, 8 Gig Memory. MacOS, Big Sur v.11.4. The error I get on an administrator account:
"You do not have permission to open the application “IPFS Desktop”. Contact your computer or network administrator for assistance." Note that I got an earlier version of IPFS to work on the prior OS before Big Sur (which was Catalina/Jazz), but it broke with Big Sur. I tried putting it in the Applications folder and using the CTRL key to open it, per the docs - no help. Bit surprised to see a desktop client fail like this - I download all sorts of smallish 3rd party apps that work fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/macos MacOS help wanted Seeking public contribution on this issue status/blocked Unable to be worked further until needs are met
Projects
None yet
Development

No branches or pull requests

7 participants