Questions around developing a new cask for "microsoft-authentication-cli" #5667
Replies: 1 comment · 4 replies
-
The cask binaries need to be signed, but even after that, it'll almost certainly be rejected in the first round:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
I actually did try to onboard First Try with homebrew formula:This is the formula script i tried, by using source code as url, and using curl and the installed script provided from
I was getting an I suspect that when installing via Homebrew, it's running in a container-like environment, which might prevent azureauth from being added to the correct path. Am I correct here? Or if you know how to fix this
Second Try with homebrew formula:I also tried to use the release package link as the url, and use
However, when i run
Thats why/how I then switched to onboard through homebrew cask with the release package link as the url and created the cask script as above. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Everything in Homebrew/core must be built from source. We do not accept pre-built binaries. If you want to ship pre-built binaries, you can ad this to Homebrew/cask. However, if the binaries are not signed and notarized, then we will not be able to accept them. This is why you are seeing those pop ups. macOS is warning you that the binaries are unsigned and can't be verified. This is an OS-level control. |
Beta Was this translation helpful? Give feedback.
All reactions
-
The binaries actually have been signed in our release pipeline for this package. So i am not sure why i am still seeing those pop ups.. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm referring to signing and notarizing as it relates to macOS: https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution |
Beta Was this translation helpful? Give feedback.
-
Output of
brew config
Output of
brew doctor
Description of issue
I am working on onboarding a new package (a CLI tool) microsoft-authentication-cli to Homebrew.
I tried to onboard microsoft-authentication-cli to Homebrew through cask. And I was able to install the package successfully on my mac machine by running
brew install
.However, when i tried to run the cli commands, for example
azureauth --version
for the first time. I keep getting the warnings such asApple could not verify "azureauth" is free of malware that may harm your mac or comporise your privacy
. I have to go tosettings -> privacy and security
and pressAllow Anyway
for all those warnings in order to make the cli command work.I have attached the cask script and some warning screenshots here.
Does anyone know why I am getting those warnings and how to bypass/fix those warnings so that I dont need to manually click the
allow
insettings -> privacy and security
?Thanks for the help in advance.
Beta Was this translation helpful? Give feedback.
All reactions