From: Jeff King <peff@peff.net>
To: Emily Ren <lingyan.ren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Can I use git protocol to push change to remote repo?
Date: Tue, 16 Dec 2008 02:38:35 -0500 [thread overview]
Message-ID: <20081216073835.GA2468@coredump.intra.peff.net> (raw)
In-Reply-To: <856bfe0e0812152322i3a7fa376h8a35466b7abf82a5@mail.gmail.com>
On Tue, Dec 16, 2008 at 03:22:17PM +0800, Emily Ren wrote:
> I can clone a remote repo with git protocol, but I can't push my
> branch to origin repo with git protocol. If I use ssh protocol, I can
> push sccuessfully. I'm confused, can someone give me a guide on this?
> Can I use git protocol to push my branch to remote repo? If yes, how
> can I do ? Thank you for your help in advance !
Yes, git-daemon does not support pushing by default, since it doesn't do
any authentication of the pushing users. The recommended practice is to
push over ssh, which uses the exact same protocol, but is tunneled over
ssh, so the user is authenticated and the incoming data has an integrity
check (note that pulling by ssh is also the same protocol as pulling via
git://, except of course that it is also tunneled over ssh; this means
that if you are pushing and pulling, you can just set your remote to
talk to the ssh version).
If you _really_ want totally anonymous, unsecured pushing to your repo
(e.g., because you are on a restricted LAN and everybody is trusted),
you can enable the receive-pack service. See the git-daemon
documentation for details.
-Peff
next prev parent reply other threads:[~2008-12-16 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <856bfe0e0812152318h1375401fx944834ad6410835d@mail.gmail.com>
2008-12-16 7:22 ` Can I use git protocol to push change to remote repo? Emily Ren
2008-12-16 7:38 ` Jeff King [this message]
2008-12-16 8:48 ` Emily Ren
2008-12-16 8:52 ` Jeff King
2008-12-16 8:59 ` Emily Ren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081216073835.GA2468@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=lingyan.ren@gmail.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.
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 NNTP newsgroup(s).