News for hackers. Stuff that matters.
Re:Remote code execution, git, and OS X by atdt on Monday April 18, 2016 @02:57AM (#11518155)
The Homebrew installation process uses the system git.
Re:Remote code execution, git, and OS X by danieldk on Monday April 18, 2016 @04:35AM (#11518477)
Yes, but if Homebrew is malicious, you'd have more problems than a specially-crafted repository that exploits a git vulnerability. You are installing something that has all user access rights.
Re:Remote code execution, git, and OS X by OJFord on Monday April 18, 2016 @06:24AM (#11518818)
You _could_ get recent git by some other means prior to installing homebrew. Anything short of compiling from source wouldn't require ever installing XCLT.
Re:Remote code execution, git, and OS X by arm on Monday April 18, 2016 @03:26AM (#11518259)
Yep, since Homebrew requires the Xcode Developer Tools to be installed (which of course includes the outdated Git).
Re:Remote code execution, git, and OS X by gpvos on Monday April 18, 2016 @04:54AM (#11518540)
Can you inunstall XCode again once you have installed a compiler, toolchain, and git via Homebrew?
Re:Remote code execution, git, and OS X by matt4077 on Monday April 18, 2016 @05:30AM (#11518667)
You can just install the command line tools without xcode. From those tools, most can be replaced with their homebrew versions so you only need them for bootstrapping. But if you want to do hardware- or OS X related development, you will need to keep the tools around. CUDA, for example, needs clang et. all.

They don't take much space, though, and the toolchain is treated a bit better by Apple than utilities like git, vim etc.

Re:Remote code execution, git, and OS X by gpvos on Tuesday April 19, 2016 @05:00AM (#11525725)
I don't know about homebrew, but macports has clang and other toolchain stuff, so I think it might be possible to uninstall Xcode after installing all necessary tools through macports?