Hi Stefan, Hi Frederik, maybe I stated the case not clearly enough. The repo is just inside an shared/mounted folder from the VM to the Host, so that we can access the sourcecode via an IDE running on the host. The git commands are executed inside the VM on an ubuntu system. So there is no mix of operating systems in the repos directly. The shared/mounted folder is underlying some restrictions, such as no filemode and case insensitive filenames. But with git we can handle this. We do not commit any file inside the .git folder. The error (could not commit .git/config file) comes up while the git-clone command executed inside the shared folder. I tried to clone the repo outside the shared folder and copied it inside afterwards. As I was doing the configuration for filemode and case with the git-config command, I got the same error (could not commit .git/config file). But I was able to update the .git/config manually. So it is not only an access problem, because I can access the file. The security risk is stated with version 2.2.1, but we were able clone in the shared folder with git 2.3. So the change must be in an higher version. Maybe I am able to install a few versions of git and try the scenario for them, then i should be able to determine the version explicit. Thanks again for your help. I hope I could state the problem a bit more detailed for you. Mit freundlichen Grüßen Peter Hüfner ......................................................... e·confirm GmbH .. Travel.Software.Training.Consulting Geschäftsführer: Roman Borch und Michael Posthoff HRB 35653B Steuernummer 37/211/10880 10119 Berlin Linienstr. 214 Tel. +49 (0) 30 28 00 28 24 Fax. +49 (0) 30 28 00 28 28 www.e-confirm.de ................................................................................................. > Am 14.07.2015 um 20:53 schrieb Stefan Beller <sbeller@xxxxxxxxxx>: > >> >>> A few weeks ago we weren’t able to clone and get an error: could not commit /vagrant/.git/config file. Manually we were able to change that file and also the clone command works outside the shared folder. >> >> Why are you trying to commit a file inside the .git dir? Files in that >> dir should not be commited (and I'm pretty sure there was a patch about >> this a while ago). The .git/config file for example is local to each git >> repo and should not be commited. > > Actually it is considered a security risk, see > http://article.gmane.org/gmane.linux.kernel/1853266 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html