On Tue, May 27, 2003 at 01:53:05PM -0400, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
For best results, use a dedicated account, and restrict the commands
that can be run in the SSH authorized_keys file.
Are you saying that you can limit the commands by some special
configuration of the
On Tue, 3 Jun 2003, at 8:56am, [EMAIL PROTECTED] wrote:
For best results, use a dedicated account, and restrict the commands that
can be run in the SSH authorized_keys file.
Are you saying that you can limit the commands by some special
configuration of the authorized_keys file? If so,
On Tue, Jun 03, 2003 at 09:50:51AM -0400, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Tue, 3 Jun 2003, at 8:56am, [EMAIL PROTECTED] wrote:
For best results, use a dedicated account, and restrict the commands that
can be run in the SSH authorized_keys file.
Are you saying that you can
'Twere it me, I'd use scp and keys. Makes SSH easier and allows for
secure copying without having to dork with passwords.
BTW, on a related note, I've been working on the same concept, but am
parsing log files from many servers into a MySQL database. Makes for
easy lookup of issues, and also
On 27 May 2003, at 1:37pm, [EMAIL PROTECTED] wrote:
I figured the best way to get the logs would be to use rsync, since i
would need to specify a password in the cron/shell script, and I know that
rsync supports a password.
Don't do that. Instead, use rsync-over-SSH, and use SSH public keys
