From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Miguel Gonz?lez Casta?os <mgc@tid.es>
Cc: linux-admin@vger.kernel.org
Subject: Re: rsync and ssh
Date: Mon, 23 Jun 2003 12:55:49 -0400 [thread overview]
Message-ID: <20030623165549.GB25076@rdlg.net> (raw)
In-Reply-To: <3EF72EFF.9405B3C7@tid.es>
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
Use "rsync -e ssh" and set up a trust. Make sure that the system
initiating the connection is very secure otherwise you've opened up a
hole with the user's ID on the remote system.
Ideal situation?
Machine A sends a file to Machine B
Create a new id "rsync-foo" on both machines with 0 privs. Make the
home dirs /var/tmp/ and a shell of /dev/null (SHOULD work with rsync).
Establish trust from A to B using the rsync-foo user ID.
rsync -e ssh -avHD -stats /source/files /target/files
Then a cron job on MachineB which validates the data and then
copies/rsync's it to it's final destination.
Robert
Thus spake Miguel Gonz?lez Casta?os (mgc@tid.es):
> dear all,
>
> I am considering to use a synchronization tool to synchronize the
> contents of some directories and mirror some directories from one server
> to another intranet server behind a dial-up connection.
>
> As you guys can imagine the speed of the connection is an issue and I
> am thinking of a system to send securely the data using some
> compression.
>
> the customer suggested rsync, I have looked through a little bit around
> the rsync website and see that there is ssh support for that tool. Which
> it would be setup for such system? Should i store the password of the
> user used for sshing the server in plain text in a file?
>
> Many thanks in advance
>
> Miguel
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Diagnosis: witzelsucht
IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net http://www.rdlg.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-23 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 16:46 rsync and ssh Miguel González Castaños
2003-06-23 16:55 ` Robert L. Harris [this message]
2003-06-23 21:10 ` Stephen Samuel
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=20030623165549.GB25076@rdlg.net \
--to=robert.l.harris@rdlg.net \
--cc=linux-admin@vger.kernel.org \
--cc=mgc@tid.es \
/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).