#The homebrew launcher 10.7 code#

If you don't have anything running as root, no programs can request that the helper execute code with privilieges without triggering a credential prompt. Closing System Preferences or simply switching back to the main view will terminate the helper and drop privileges. I considered this a reasonable tradeoff between security, usability and code simplicity. As such, it is possible that if LaunchRocket's AppleScript helper has cached your privileged authorization, another application maliciously address that helper and request it execute other commands with root level privileges. This is not the most secure approach and does not use code signing.

#The homebrew launcher 10.7 install#

This is a hacky way of accomplishing it, but it avoids having to actually install a privileged helper outside of the prefpane bundle with SMJobBless and is WAY simpler. LaunchRocket uses an AppleScript helper to obtain root privileges. As of it is no longer maintained in my personal tap, and is now available in the main Homebrew Cask repo.ДЇurther information about running as root Launchrocket is available as a Cask for Homebrew Cask. I will try to provide a more compatible zipfile on the releases page. I've heard that there are issues unzipping it with other tools. Note: This zip was created with Finder's 'Compress' utility. The latest builds are compiled on 10.9.1 and targeted at 10.7 in Xcode.Дownload and unzip the binary release from the release page

#The homebrew launcher 10.7 mac osx#

The binary release should work on Mac OSX 10.7.0 and above, and might even work on older versions, though it has not been tested on those.

Gatekeeper must be set to allow all apps to run (See issues #3 and #25).

LaunchRocket stores a preferences file in ~/Library/Preferences/.

This means that if you have services running as root, it will prompt you for credentials immediately on load, as an unprivileged account cannot even list launchd services run by a privileged one We ask for credentials as seldom as possible, however when launchrocket loads, it checks the current status of every service it's tracking.LaunchRocket will prompt you to authenticate and elevate privileges.Checking this will NOT restart a running service automatically as root.Checking this will cause launchrocket to use root privileges to access launchctl.Dynamically updates state based on running state of service.Red - launchctl reports process is not running.Yellow - LaunchRocket is current executing or waiting on a start/stop command.Green - launchctl reports process is running.I recommend you only run things as root if you absolutely must, to get them working properly. For example, many times it's just easier to run Apache on port 80 and 443 than to deal with code that might not like port numbers in the URLs.

However, some services (dnsmasq) require being bound to privileged ports, and others (nginx, apache) don't require it, but might in some circumstances. With Homebrew, most services can simply run as the current user, and this is the desired behavior for a development environment. Of particular note is the ability to run some services as root. LaunchRocket was primarily created for managing various services installed by Homebrew, though it should work with most launchd-compatible plists. A Mac PreferencePane for managing services with launchd.