-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
wd-security 2.1.2.144 (new cask) #173945
wd-security 2.1.2.144 (new cask) #173945
Conversation
/rebase |
1726784
to
471291c
Compare
The installer prompts for macOS user password in an "app wants to make changes" dialog. Running with sudo still requests it. Any way to handle this for the TestBot? |
@unitof Casks shouldn't require user intervention outside of entering your password in terminal for sudo when required. So unfortunately this is a blocking issue. |
The Gatekeeper prompt is slightly different in my testing (TouchID instead of password prompt) so may pass tests
@unitof We're close here now
|
Huh. Any other approaches or places I should look for more info? |
It may not be being removed because it is still running, so what I tried may not be actually closing it. |
Will maintain here, since cask permissions are too weird for official cask Homebrew/homebrew-cask#173945
Obscure and kinda dusty app, but used by the very popular Backblaze software for their mailed restore drives
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
In the following questions
<cask>
is the token of the cask you're submitting.After making any changes to a cask, existing or new, verify:
brew audit --cask --online <cask>
is error-free.brew style --fix <cask>
reports no offenses.Additionally, if adding a new cask:
brew audit --cask --new <cask>
worked successfully.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask>
worked successfully.brew uninstall --cask <cask>
worked successfully.