On Fri, Apr 06, 2001 at 02:40:43PM +1000, Greg Burley wrote:
> Harry Putnam wrote:
> > I want only binary-all/ binary-i386/ and disks-i386
> >
> > My command line looks like:
> > rsync -navvz --exclude-from=rsync_woody_exclude
> > rsync://ftp.debian.org/debian/dists/woody/ .
> >
> > I
On Thu, Apr 05, 2001 at 11:38:22AM -0400, Randy Kramer wrote:
> However, I guess I wasn't very clear, the point of touching the local
> file was to create a mismatch between the date and time of the local
> copy and the remote copy. Would the -c option do something more than
> would be done based
I've had problems with rsync on disk-disk transfers if I use the -v
option. Try it again without -v.
--Yan
"M. Drew Streib" wrote:
>
> On Thu, Apr 05, 2001 at 11:38:22AM -0400, Randy Kramer wrote:
> > However, I guess I wasn't very clear, the point of touching the local
> > file was to create
I'm trying to create a nearline archive.
I don't have another volume big enough to hold a full backup of the
master volume, so I can't compare the change set in the usual way.
I would just like to get whatever was modified in the last day - like
the results of a find -mtime 1 (or 0) would give. S
Is there a way to have rsync not prompt for a password.
I've tried using .shosts and also the authorized_keys files,
but neither seem to work. Is there anyway to modify the
rsh or ssh commands that rsync uses?
I don't know the password of the user that rsync will need
to run under, though I ca
On Fri, Apr 06, 2001 at 05:42:25PM -0600, David Salisbury wrote:
> Is there a way to have rsync not prompt for a password.
> I've tried using .shosts and also the authorized_keys files,
> but neither seem to work. Is there anyway to modify the
> rsh or ssh commands that rsync uses?
I assume you
Might there be a good set of tutorials on the web on
how to do this while minimizing the risk of exposing
systems as a consequence? (setup of private/public
identity files that minimize the risk of hackers getting
passwordless access to other remote machines).
I must admit hating the passwordl
Lachlan,
Excuse me for jumping into this discussion, especially being something
of a newbie.
As I understand ssh without passwords, it is very secure because it is
based on a public / private key scheme, something like PGP. When you
set up a passwordless ssh system, you create a public and priv
On Fri, Apr 06, 2001 at 09:33:04PM -0400, Randy Kramer wrote:
> Now, I may be wrong in my understanding, but, for a moment, please
> assume I'm right. If I am right, and the security provided by a
> passwordless ssh connection is just as good as, for example, PGP (assume
> I'm right about that to
Hi Randy (and rsync list),
(Before waffling on a side tracked issue - there is still a
request for good web based passwordless ssh tutorials)
I must apologise as usual for poor elaboration of my
paranoia against passwordless ssh.
I roughly agree with your assessment. However, the thing that
>As for implementing ssh inside of rsync, I'd like to continue to reiterate
>what a bad idea I think that is. Security is enough pain without worrying
>about every program carrying its own security model and implementation (and
>possible exploits).
What if such a feature was an optional module t
Hello Lachlan,
Lachlan Cranswick wrote:
> (Before waffling on a side tracked issue - there is still a
> request for good web based passwordless ssh tutorials)
I don't really have anything to offer -- I learned some about public /
private key systems over a lot of years starting with a signature
>Not fully understanding the ramifications of chroot (as a Linux newbie)
>I don't really know whether limiting someone's access by chrooting is
>any more effective than limiting his access based on privileges provided
>to his account.
Re: rsync, ssh, security and keeping hackers out. (just my
13 matches
Mail list logo
