public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: git-push through git protocol
Date: Sun, 21 Jan 2007 16:27:28 +0100	[thread overview]
Message-ID: <ep00nl$mop$1@sea.gmane.org> (raw)
In-Reply-To: 17843.29798.866272.414435@lisa.zopyra.com

[Cc: git@vger•kernel.org]

Bill Lear wrote:

> We have a secure network in which we run all of our git-supported
> development activities.  We would like to be able to do git-push
> through the git protocol.  Reasons: 1) it seems more efficient; 2) we
> have run into problems with developers having different umasks ---
> when run through ssh, we ran into file permissions problems and
> instead of tracking down each umask issue the developer has (and,
> frankly, not wanting to change their default), we resorted to fixing
> up the permissions inside of the update hook (chmod -R ug+w, I think);
> 3) we would prefer a single protocol instead of sometimes pulling with
> git and pushing with ssh.
> 
> It seems there should be a way to configure a repo or the git daemon
> to say "Allow push operations".
> 
> I looked through the release notes Junio posted for 1.5.0-rc2, but
> found no reference to the git daemon.

git:// protocol is not authenticated. git by design allow push only through
authenticated protocols, i.e. local, ssh:// (git+ssh://), http(s):// with
WebDAV, probably in the future ftps://. 

rsync:// (deprecated) and git:// are fetch only (read-only) protocols.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-01-21 15:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 14:10 git-push through git protocol Bill Lear
2007-01-21 15:27 ` Jakub Narebski [this message]
2007-01-21 19:04   ` Linus Torvalds
2007-01-21 20:09     ` Bill Lear
2007-01-21 21:16     ` Johannes Schindelin
2007-01-21 21:22     ` Bill Lear
2007-01-21 22:00       ` Linus Torvalds
2007-01-22  0:17         ` Linus Torvalds
2007-01-22  0:50           ` Junio C Hamano
2007-01-22  1:10           ` [PATCH] Make sure git_connect() always give two file descriptors Junio C Hamano
2007-01-22  1:47             ` Linus Torvalds
2007-01-22  1:31         ` git-push through git protocol Bill Lear
2007-01-22  1:41           ` Bill Lear
2007-01-22  1:52           ` Linus Torvalds
2007-01-22  2:26             ` Martin Langhoff
2007-01-22  3:01               ` Linus Torvalds
2007-01-22 13:58                 ` Bill Lear
2007-01-22 14:41             ` Bill Lear
2007-01-21 23:49 ` Martin Langhoff
2007-01-22  0:03   ` Bill Lear
2007-01-22  0:24     ` Martin Langhoff
2007-01-22  0:48       ` Jakub Narebski

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='ep00nl$mop$1@sea.gmane.org' \
    --to=jnareb@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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