From: "Peter Hüfner" <p.huefner@e-confirm.de>
To: Stefan Beller <sbeller@google.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git on vagrant shared folder
Date: Thu, 16 Jul 2015 09:09:33 +0200 [thread overview]
Message-ID: <ABFD6E6C-A59B-49FB-8B39-D86F00EA2A8D@e-confirm.de> (raw)
In-Reply-To: <CAGZ79kbBKzbjbg5u7A7BgnV1JF=5A+-gb0OdYs11g6kx_UQu_A@mail.gmail.com>
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@google.com>:
>
>>
>>> 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
next prev parent reply other threads:[~2015-07-16 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 15:49 git on vagrant shared folder Peter Hüfner
2015-07-14 18:32 ` Fredrik Gustafsson
2015-07-14 18:53 ` Stefan Beller
2015-07-16 7:09 ` Peter Hüfner [this message]
2015-07-16 16:41 ` Junio C Hamano
2015-07-20 7:26 ` Peter Hüfner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABFD6E6C-A59B-49FB-8B39-D86F00EA2A8D@e-confirm.de \
--to=p.huefner@e-confirm.de \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).