git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aaron Gray" <aaronngray.lists@googlemail.com>
To: "Julian Phillips" <julian@quantumfyre.co.uk>
Cc: <git@vger.kernel.org>
Subject: Re: git & ssh on F10 server
Date: Sat, 18 Apr 2009 16:12:32 +0100	[thread overview]
Message-ID: <DD909F216D254CDAB2A0C0847AEB75C0@HPLAPTOP> (raw)
In-Reply-To: alpine.LNX.2.00.0904171812330.8773@reaper.quantumfyre.co.uk

> On Fri, 17 Apr 2009, Aaron Gray wrote:
>>>  On Fri, 17 Apr 2009, Aaron Gray wrote:
>>>
>>> >  Hi,
>>> >
>>> >  we have a Fedora 10 server in SELinux enforcing mode setup running 
>>> > git-deamon and gitweb (with home grown SElinux policy).
>>> >
>>> >  Anyway now we find out you cannot do a 'push' over the basic git 
>>> > protocol, back to the server repository.
>>>
>>>  You can push over git://, but you get no authentication mechanism so 
>>> it's
>>>  disabled by default.  It's only really useful if you trust everyone who
>>>  has IP access to the server.
>>
>> How do go about I enabling it ?
>
> You have to enable the receive-pack service.  You can either enable it for 
> all repositories by using the --enable=<service> option to git-daemon, or 
> on a per-repository basis by setting daemon.receivepack to true in the 
> repositories that you want to enable push for.

Okay I have added the following to 'config' :-

[daemon]
        receivepack = true

and done an 'service xinetd restart' just in case, probably not needed.

I have tried a 'git push git://.../repo' but it is hanging, btw I am using 
Cygwin on the client, and F10 on the server.

Trying to clone an empty repository also hangs. btw I have sucessfully 
cloned big repositories.

Aaron

>>> >  So now am trying to get git to work over ssh. The repositories are 
>>> > located /pub/git/*/.git
>>> >
>>> >  Basic attempts using BerliOS'es instructions for client end failed.
>>> >
>>> >
>>> > 
>>> > http://developer.berlios.de/docman/display_doc.php?docid=1812&group_id=2
>>> >
>>> >  Could someone please help us with this.
>>> >
>>> >  Aaron
>>>
>>>  You haven't said what commands you tried, nor what the errors you 
>>> received
>>>  were, so it's a bit hard to say what went wrong ...
>>>
>>
>> git push ssh://ang@git.site.org/pub/git/llvm/trunk milestone1
>> Pushing to ssh://ang@git.site.org/pub/git/llvm/trunk
>> fatal:  exec ssh failed.
>> fatal:  The remote end hung up unexpectedly
>
> Sounds like git didn't find ssh on your path.
> What version of git is this btw?
>
>> A clone failed simularly
>>
>> I was expecting it to ask for a password. Should I try a DSA certificate 
>> ?
>>
>> Thanks,
>>
>> Aaron
>>
>>
>
> -- 
> Julian
>
>  ---
> "It's my cookie file and if I come up with something that's lame and I 
> like it,
> it goes in."
> -- karl (Karl Lehenbauer) 

  parent reply	other threads:[~2009-04-18 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 15:56 git & ssh on F10 server Aaron Gray
2009-04-17 16:19 ` Julian Phillips
     [not found]   ` <FD77671D77E2465097BD60A1E144BB91@HPLAPTOP>
2009-04-17 17:17     ` Julian Phillips
2009-04-17 18:00       ` Aaron Gray
2009-04-18 15:12       ` Aaron Gray [this message]
2009-04-18 15:34         ` Julian Phillips
2009-04-18 15:58           ` Aaron Gray
2009-04-18 18:07           ` push git: failing Aaron Gray
2009-04-18 15:37       ` git & ssh on F10 server Aaron Gray

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=DD909F216D254CDAB2A0C0847AEB75C0@HPLAPTOP \
    --to=aaronngray.lists@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    /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).