Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git
brew update will use `git clone`, so yeah...
Git client vulnerability announced
41–50 of 191 posts
Re: Git client vulnerability announced
#42Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git
brew update will use `git clone`, so yeah...
Re: Git client vulnerability announced
#43> We have also completed an automated scan of all existing content on github.com to look for malicious content that might have been pushed to our site before this vulnerability was discovered did they find any problems? The post doesn't say...
Vicent Marti (from GitHub) states: "In case it's not obvious from the post: There are no malicious repos in @github and they can't be pushed anymore. Update your Git anyway." https://twitter.com/vmg/status/545693913491984385
Re: Git client vulnerability announced
#44Earlier quoted context omitted.
The announcement includes several links to binaries. Is there one you need that's missing?
The blog post on Github.com only includes links to Github for Mac binaries, not git proper. The link in the blog post to kernel.org has tarballs of source, not binaries. Did I miss something?
Re: Git client vulnerability announced
#45Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git
Re: Git client vulnerability announced
#46Earlier quoted context omitted.
It's a very high priority, because there are things that transparently use Git and don't host all their repositories on Github. Update ASAP.
Yeah, but typically you have a certain level of trust in your project dependencies. Adding a library to your project often means granting access to your system anyway (if the dependency contains executable code).
Re: Git client vulnerability announced
#47Re: Git client vulnerability announced
#48Earlier quoted context omitted.
Wow downvoting because I ask for binaries instead of source? Majority of people reading this want a fast, immediate solution from a trustworthy source. edit: obvious places still haven't updated. git-scm still provides 6-month-old binaries
[deleted]
Re: Git client vulnerability announced
#49Should programs periodically check for critical security fixes, and then refuse to run if the current version is affected? It seems like there are a lot of people who don't really pay attention to social media or other security alert channels, who won't have a clue about the extent of this vulnerability. I'm sure they'd update if they knew "if I clone a malicious repo, I'm toast," but there's no way to inform them ex…
Re: Git client vulnerability announced
#50Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git
I keep getting fatal: unable to access 'https://github.com/Homebrew/homebrew/': The requested URL returned error: 503 Error: Failure while executing: git pull -q origin refs/heads/master:refs/remotes/origin/master Weird, it's the first time it's ever happened. edit: wait, it worked after a couple of tries; maybe it's due to panicked people updating brew\git?