> > 3) Add this to authorized_keys for the above account, specifying the
> > command that logins with this key are allowed to run. See command="" in
> > sshd(1).
>
> I can't find the document about this section, can you show me
> some reference or examples? Many thanks.
man sshd, down the botto
> > 3) Add this to authorized_keys for the above account, specifying the
> > command that logins with this key are allowed to run. See command="" in
> > sshd(1).
>
> I can't find the document about this section, can you show me
> some reference or examples? Many thanks.
man sshd, down the bott
> 3) Add this to authorized_keys for the above account, specifying the
> command that logins with this key are allowed to run. See command="" in
> sshd(1).
I can't find the document about this section, can you show me
some reference or examples? Many thanks.
--
Patrick Hsieh <[EMAIL PROTECTED]>
> 3) Add this to authorized_keys for the above account, specifying the
> command that logins with this key are allowed to run. See command="" in
> sshd(1).
I can't find the document about this section, can you show me
some reference or examples? Many thanks.
--
Patrick Hsieh <[EMAIL PROTECTED]>
[cc: trimed to something a little more sane]
On Wed, Jan 02, 2002 at 04:21:33PM -0500, [EMAIL PROTECTED] wrote:
> We're pulling **from** a read-only rsyncd. It has to run as root because we
> require the right archive, permissions, etc I'm confused; is that much
> different from running an
On Wed, Jan 02, 2002 at 10:17:38AM -0800, Ted Deppner wrote:
> > The [modules] in rsyncd.conf provide a nice way to package what you want to
> > back up. You can also specify what ip addresses connect to rsyncd. So in
> > theory only the backup machine can connect to the rsyncd daemons; we've se
[cc: trimed to something a little more sane]
On Wed, Jan 02, 2002 at 04:21:33PM -0500, [EMAIL PROTECTED] wrote:
> We're pulling **from** a read-only rsyncd. It has to run as root because we
> require the right archive, permissions, etc I'm confused; is that much
> different from running an
On Wed, Jan 02, 2002 at 10:17:38AM -0800, Ted Deppner wrote:
> > The [modules] in rsyncd.conf provide a nice way to package what you want to
> > back up. You can also specify what ip addresses connect to rsyncd. So in
> > theory only the backup machine can connect to the rsyncd daemons; we've s
On Wed, Jan 02, 2002 at 09:19:11AM -0500, [EMAIL PROTECTED] wrote:
> Automation with keys stored on machines is better than doing it manually
> and forgetting to back up. :-)
Agreed. Like excercise, the kind you do is better than the kind you
don't.
> It **does** provide a path by which someone
On Wed, Jan 02, 2002 at 09:19:11AM -0500, [EMAIL PROTECTED] wrote:
> Automation with keys stored on machines is better than doing it manually
> and forgetting to back up. :-)
Agreed. Like excercise, the kind you do is better than the kind you
don't.
> It **does** provide a path by which someon
ssh-agent does help here. Have the cron job which is doing the backup
look to see if there's an ssh agent running as its user (presumably
'backup', maybe root) and if not send mail to somebody's pager,
complaining about the missing agent. If the agent is running, the
cron job can reconnect to it
On Wed, Jan 02, 2002 at 03:35:43PM +0800, Patrick Hsieh wrote:
> OK. My problem is, if I use rsync+ssh with blank passphrase among
> servers to automate rsync+ssh backup procedure without password prompt,
> then the cracker will not need to send any password as well as
> passphrase when ssh login o
ssh-agent does help here. Have the cron job which is doing the backup
look to see if there's an ssh agent running as its user (presumably
'backup', maybe root) and if not send mail to somebody's pager,
complaining about the missing agent. If the agent is running, the
cron job can reconnect to i
On Wed, Jan 02, 2002 at 03:35:43PM +0800, Patrick Hsieh wrote:
> OK. My problem is, if I use rsync+ssh with blank passphrase among
> servers to automate rsync+ssh backup procedure without password prompt,
> then the cracker will not need to send any password as well as
> passphrase when ssh login
> OK. My problem is, if I use rsync+ssh with blank passphrase among servers
> to automate rsync+ssh backup procedure without password prompt, then the
> cracker will not need to send any password as well as passphrase when ssh
> login onto another server, right?
No, password and rsa/dsa authenti
Hello Ted,
Your mail is very informative to me.
I wonder how to define cmd to run automatically in authorized_hosts?
I thought there's nothing but pub keys in authorized_hosts file.
And, do I need ssh-agent in this case? Do I need to leave passphrase
blank?
Thank you for your patience and kindne
> OK. My problem is, if I use rsync+ssh with blank passphrase among servers
> to automate rsync+ssh backup procedure without password prompt, then the
> cracker will not need to send any password as well as passphrase when ssh
> login onto another server, right?
No, password and rsa/dsa authent
On Wed, Jan 02, 2002 at 03:15:20PM +0800, Patrick Hsieh wrote:
> I've read some doc. using ssh-keygen to generate key pairs, appending
> the public keys to ~/.ssh/authorized_hosts on another host to prevent
> ssh authentication prompt. Is it very risky? Chances are a cracker could
> compromise one
OK. My problem is, if I use rsync+ssh with blank passphrase among
servers to automate rsync+ssh backup procedure without password prompt,
then the cracker will not need to send any password as well as
passphrase when ssh login onto another server, right?
Is there a good way to automate rsync+ssh p
> I am sorry I could be kind of off-topic. But I want to know how to
> cross-site rsync without authentication, say ssh auth.,?
That's the best way.
> I've read some doc. using ssh-keygen to generate key pairs, appending the
> public keys to ~/.ssh/authorized_hosts on another host to prevent ss
Hello,
I am sorry I could be kind of off-topic. But I want to know how to
cross-site rsync without authentication, say ssh auth.,?
I've read some doc. using ssh-keygen to generate key pairs, appending
the public keys to ~/.ssh/authorized_hosts on another host to prevent
ssh authentication prompt.
Hello Ted,
Your mail is very informative to me.
I wonder how to define cmd to run automatically in authorized_hosts?
I thought there's nothing but pub keys in authorized_hosts file.
And, do I need ssh-agent in this case? Do I need to leave passphrase
blank?
Thank you for your patience and kindn
On Wed, Jan 02, 2002 at 03:15:20PM +0800, Patrick Hsieh wrote:
> I've read some doc. using ssh-keygen to generate key pairs, appending
> the public keys to ~/.ssh/authorized_hosts on another host to prevent
> ssh authentication prompt. Is it very risky? Chances are a cracker could
> compromise one
OK. My problem is, if I use rsync+ssh with blank passphrase among
servers to automate rsync+ssh backup procedure without password prompt,
then the cracker will not need to send any password as well as
passphrase when ssh login onto another server, right?
Is there a good way to automate rsync+ssh
> I am sorry I could be kind of off-topic. But I want to know how to
> cross-site rsync without authentication, say ssh auth.,?
That's the best way.
> I've read some doc. using ssh-keygen to generate key pairs, appending the
> public keys to ~/.ssh/authorized_hosts on another host to prevent s
Hello,
I am sorry I could be kind of off-topic. But I want to know how to
cross-site rsync without authentication, say ssh auth.,?
I've read some doc. using ssh-keygen to generate key pairs, appending
the public keys to ~/.ssh/authorized_hosts on another host to prevent
ssh authentication prompt
26 matches
Mail list logo
