Re: ssh catch 22

2006-11-14 Thread Ed
I'll be honest, I was about to send a long mail on how it still doesn't work... when it suddenly did! :) So I thought some poor soul might like a step by step so here it is 192.168.1.1 is the source with the data you want 192.168.1.2 is the destination where you want the data to go with that

Re: ssh catch 22

2006-11-13 Thread Ed
On Wednesday 08 November 2006 00:34, Ed wrote: On Tuesday 07 November 2006 22:53, you wrote: ...snip... You want to run the rsync command upon connection. Try to use: command=/usr/bin/rsync --server --daemon --config=/foo/rsyncd.conf .

Re: ssh catch 22

2006-11-13 Thread Wayne Davison
On Tue, Nov 07, 2006 at 07:19:31PM +0100, Ed wrote: b) in the certificate, I specified the command that could be run... the likes of: command=rsync -av ./source [EMAIL PROTECTED]:/destination ssh-rsa It's completely invalid to specify a client command when expecting a server command. Just run

ssh catch 22

2006-11-07 Thread Ed
Hi all, I'm stuck with a little dilemma and I thought someone could give me a little advice. Is there a way to use rsync with an ssh certificate? what I have: First of all I am forced to use the root account with ssh which I know is a big no, no, but sometimes it can't be

Re: ssh catch 22

2006-11-07 Thread David Tonhofer
Ed wrote: Hi all, I'm stuck with a little dilemma and I thought someone could give me a little advice. Is there a way to use rsync with an ssh certificate? There should be what I have: First of all I am forced to use the root account with ssh which I know is a big no,

Re: ssh catch 22

2006-11-07 Thread Ed
On Tuesday 07 November 2006 22:53, you wrote: ...snip... You want to run the rsync command upon connection. Try to use: command=/usr/bin/rsync --server --daemon --config=/foo/rsyncd.conf . ,no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty ssh-rsa [BASE64-encoded data of