http://mercurial.selenic.com/wiki/WhatsNew#Mercurial_3.2.3_....
You'll need 3.2.3 to be secure.
So, update no matter what, unless you're not on an affected system?
(this is a question, not a statement)
I know of three: FAT (specifically vfat, these days), JFS with Option -O, and CIOPFS (Case Insensitive On Purpose Filesystem):
http://superuser.com/questions/290480/case-insensitive-parti...
http://linux.die.net/man/8/mkfs.jfs
http://manpages.ubuntu.com/manpages/hardy/man8/jfs_mkfs.8.ht...
http://www.brain-dump.org/projects/ciopfs/
Are there any more?
There are others that would be exotic these days, like AFP. And with FUSE, could be anything.
That is: $ zfs get casesensitivity zroot NAME PROPERTY VALUE SOURCE zroot casesensitivity sensitive -
Is what you want in general. Unless you have some reason not to be, in which case you have to worry about the bug.
Also, can git run with .git/config being read only? That could be a useful second line of defense.
edit: Nevermind, short-lived issue. Just upgraded to 2.2.1.
brew update
brew upgrade gitEDIT: Macports just updated. I did it with
# port selfupdate # port upgrade outdated
and 2.2.1 came down.
If you have the Apple git, then you should
# port install git
Summary: on case-insensitive/normalizing filesystems (default on OSX and Windows) it's possible for .git/config to be overwritten by the tree, probably due to a case-sensitive sanity check when the actual file is insensitive. .git/config can contain arbitrary commands to be run on certain events/as aliases, so it leads to code execution. This is a risk when you get a tree from a third party, so on pull/fetch+checkout/clone...
There's an analogous vulnerability in Mercurial.
Update, then run git --version and make sure it's one of v1.8.5.6, v1.9.5, v2.0.5, v2.1.4, or v2.2.1. And be careful when pulling/cloning from third-parties.
EDIT: right, no "or", what are you doing reading this instead of updating?