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

bitwarden/bws is not verified by Apple and cannot run without special permissions #334

Closed
1 task done
saxelsen opened this issue Nov 17, 2023 · 3 comments
Closed
1 task done
Labels
bug Something isn't working

Comments

@saxelsen
Copy link

Steps To Reproduce

On MacOS 13.2.1:

  1. Download the pre-built binary for Mac: bws-macos-universal-0.3.1.zip
  2. Unpack it
  3. Run the CLI tool in the terminal $: bws

Expected Result

After unpacking the executable I expect to be able to run it. Ideally instead of downloading it, it would be available through a package manager like Homebrew.

Actual Result

The MacOS system shows an alert saying "bws cannot be opened because the developer cannot be verified." and gives the option to either close the pop-up or move the executable to the Trash.

I think you need to notarize and sign the executable as part of your release pipeline. Not doing it is likely preventing a lot of your MacOS users from adopting your tools. There is a way to let the OS trust the app anyway, but it is hidden away in the settings.

Screenshots or Videos

No response

Additional Context

No response

Operating System

macOS

Operating System Version

13.2.1

Shell

Zsh

Build Version

0.3.1

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@saxelsen saxelsen added the bug Something isn't working label Nov 17, 2023
@Hinton
Copy link
Member

Hinton commented Nov 23, 2023

Hi @saxelsen,

Code signing and notarizing is definitely something we want to do. I know it's on the teams backlog but I don't have any specific timeline.

I believe right clicking and selecting open in the context menu will prompt gatekeeper to allow the binary and avoid the trip to settings.

@drunknbass
Copy link

+1
Not being notarized makes setting this up on remote machines(CI/CD) more difficult.

@Hinton
Copy link
Member

Hinton commented Mar 15, 2024

This was resolved in #535, and should be included in the next CLI release.

@Hinton Hinton closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants