using rsync to backup windows workstations
tim.conway at philips.com
tim.conway at philips.com
Thu Nov 15 04:12:27 EST 2001
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
PermitEmptyPasswords no
this REQUIRES that a password be used,
Tim Conway
tim.conway at philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"Thomas Lambert" <thomas at dscassociates.com>
Sent by: rsync-admin at lists.samba.org
11/14/2001 10:05 AM
To: <rsync at lists.samba.org>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Re: using rsync to backup windows workstations
Classification:
OK, I might be actually getting this. Here is part of my sshd_config file
RhostsAuthentication no
#
# For this to work you will also need host keys in
/etc/ssh/ssh_known_hosts
RhostsRSAAuthentication no
#
RSAAuthentication yes
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
PermitEmptyPasswords no
# Comment to enable s/key passwords or PAM interactive authentication
# NB. Neither of these are compiled in by default. Please read the
# notes in the sshd(8) manpage before enabling this on a PAM system.
ChallengeResponseAuthentication no
Do I just need to change the last line to yes
(ChallengeResponseAuthentication yes) and then when I generate my key on
the
NT box, put in a passphrase.
Or I could change the PermitEmptyPasswords to yes, and then I would not
need
to put in a passphrase when I generate the key.
Am I getting close or still WAY OFF?
----- Original Message -----
From: <tim.conway at philips.com>
To: "Thomas Lambert" <thomas at dscassociates.com>
Cc: <rsync at lists.samba.org>
Sent: Wednesday, November 14, 2001 11:26 AM
Subject: Re: using rsync to backup windows workstations
> I"m guessing it's in /etc/sshd_config.
> ssh issue, not rsync.
> try "ssh linuxbox uname -a" from a windoze machine. if that doesn't
work
> without a password, neither will rsync.
> >From "man sshd":
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> PasswordAuthentication
> Specifies whether password authentication is allowed. The de-
> fault is ``yes''. Note that this option applies to both protocol
> versions 1 and 2.
>
> PermitEmptyPasswords
> When password authentication is allowed, it specifies whether
the
> server allows login to accounts with empty password strings. The
> default is ``no''.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> If PasswordAuthentication is yes, then you'll need to ensure that
> PermitEmptyPasswords is also yes, or you won't be allowed passphraseless
> authentication.
> If you're not permitted to change that, just use a simple ssh
passphrase.
> >From "man rsync":
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Some paths on the remote server may require authentication.
> If so then you will receive a password prompt when you con-
> nect. You can avoid the password prompt by setting the
> environment variable RSYNC_PASSWORD to the password you want
> to use or using the --password-file option. This may be use-
> ful when scripting rsync.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Wonderful thing, those man pages.
> Good luck.
>
> Tim Conway
> tim.conway at philips.com
> 303.682.4917
> Philips Semiconductor - Longmont TC
> 1880 Industrial Circle, Suite D
> Longmont, CO 80501
> Available via SameTime Connect within Philips, n9hmg on AIM
> perl -e 'print pack(nnnnnnnnnnnn,
> 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
> ".\n" '
> "There are some who call me.... Tim?"
>
>
>
>
> "Thomas Lambert" <thomas at dscassociates.com>
> Sent by: rsync-admin at lists.samba.org
> 11/14/2001 08:15 AM
>
>
> To: <rsync at lists.samba.org>
> cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
> Subject: Re: using rsync to backup windows workstations
> Classification:
>
>
>
> I have about 12 NT servers that I want to backup 1 directory to my Linux
> Server. The problem I am having is trying to get it not to ask for the
> user's password. I am trying to use ssh. I just installed the latest
> cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was
on
> the NT machine, I ran ssh-keygen (no passphrase) and then added the
> identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys.
> When I run:
> rsync -uv -e ssh *.* thomas at linuxbox:backup/
> it asks for a password. Besides asking for the password, it works fine.
> Only the files changed are updated and it is FAST! I saw the ssh-agent.
Do
> I need to use it? and how? Is there something I need to do on my Linux
> server? I am pretty new to Linux, and have a long way to go to be an
> "expert", but I can get around.
>
> Thanks for any help.
>
> Thomas Lambert
> VP
> DSC Associates, Inc.
> thomas at dscassociates.com
>
> ----- Original Message -----
> From: "Lapo Luchini" <lapo at lapo.it>
> To: <rsync at lists.samba.org>
> Sent: Tuesday, November 13, 2001 5:23 PM
> Subject: Re: using rsync to backup windows workstations
>
>
> > As officially I'm the mantainer of cygwin's rsync package I feel I
must
> add
> > something.. 0=)
> >
> > > a) rsync binaries for win32/cygwin are now available from the
binaries
> > > section of the rsync web pages, maintained by someone at redhat I
> think
> >
> > Maintained by me, I don't work for redhat, and sadly I have a bit too
> little time
> > to maintain it as I should...
> >
> > > b) the version attached is so old that you really shouldn't attempt
to
> use it.
> > > Get the latest CVS version and add Wayne Davison's patches (see
> > > mailing list archives), in particular for use with Windoze
systems,
> > > then compile it yourself with cygwin
> >
> > ...but not so little not to compile it with Wayne's patches (actual
> patch
> is the
> > latest anti-hang available at the date of the release of cygwin's
> rsync-2.4.6-2
> > package) ;-)
> >
> > If there's some patch that I missed (I read this mailing list since
when
> I
> began to
> > mantain that package, but reading only headers of most messages maybe
I
> missed
> > something...) please point it to me and I'll release a new verison
> shortly
> =)
> >
> > Please note that I'm not an "expert programmer" of rsync, just a
person
> that likes
> > and uses it (and wants maybe to become such an expert, btw): in cygwin
> one
> package
> > can't exist in the distribution if there's not a mantainer... so I
hope
> that the
> > effort I put in it is not wasted, even if it's maybe not enough...
[I've
> got a bit
> > of guild for that eheh]
> >
> > > c) it's easy to compile under cygwin, and cygwin is easy to install,
> so
> I
> > > strongly recommend doing that
> >
> > That's true, it compiles out-of-the box.
> > The main problem is that in winsocks if the socket is closed a RST is
> sent, not
> > flushing the cache.
> > This creates many errors at the end of trasnfer, especially in the
> daemon
> mode
> > (which is not addressed by the patch I used, I bet).
> >
> > > d) also install openssh which compiles cleanly under cygwin and is
> much
> > > more reliable than the ssh that is attached here
> >
> > Compiles cleanly and is available as a binary.
> >
> > If anyone wants to ask some more question.. feel free, even if I don't
> know nothing
> > "special" about it, as I said I had not had the time to completely
study
> and
> > understand rsync source...
> >
> > C ya,
> > Lapo
> >
> > --
> > Lapo Luchini
> > lapo at lapo.it (PGP & X.509 keys available)
> > http://www.lapo.it (ICQ UIN: 529796)
> >
> >
> >
>
>
>
>
>
>
>
More information about the rsync
mailing list