Backup Central

I just tried backing up an ancient RH6 server with backuppc. Looks like the
rsync version installed there (2.3.1) uses rsync protocol 20.

I'm presuming this is not supported by whatever perl module backuppc uses
for rsync; since the connection just sort of hangs and nothing happens.

am I correct in this guess; and I need to upgrade rsync on this box?
quick yes/no confirmation is all I'm looking for here; in case I'm missing
something.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Am Donnerstag 03 Juni 2004 17:36 schrieb Carl Wilhelm Soderstrom:
I just tried backing up an ancient RH6 server with backuppc. Looks like the
rsync version installed there (2.3.1) uses rsync protocol 20.

I'm presuming this is not supported by whatever perl module backuppc uses
for rsync; since the connection just sort of hangs and nothing happens.

am I correct in this guess; and I need to upgrade rsync on this box?
quick yes/no confirmation is all I'm looking for here; in case I'm missing
something.

I don't know if this version is supported. But because you have problems with
this version I would guess that this rsync version is too old.

But you should upgrade to a up-to-date version anyway, because there have been
(I think) 2 bugs in rsync that may allow evil hackers to transfer/delete
files that they normaly should not see.

At least for the last problem there is no official redhat patch for this,
because redhat stopped supporting the normal redhat series since 01/2004.

See: http://rsync.samba.org/ for more details and the newest sourcecode.

--Ralph

P.s.: You should think of upgrading the complete box to a up-to-date distro
with a working security update system anyway, because if you want to keep old
redhat server secure you have at least ten times the work as for a normal
up-to-date system, because there will be no more fixes from redhat for this
kind of system and so you have to patch all own your own :/


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

But you should upgrade to a up-to-date version anyway, because there have been
(I think) 2 bugs in rsync that may allow evil hackers to transfer/delete
files that they normaly should not see.

that's only if you're running rsyncd; which we are not. (and do not do
anywhere). but yeah, I know what you mean.

At least for the last problem there is no official redhat patch for this,
because redhat stopped supporting the normal redhat series since 01/2004.

<snip>

P.s.: You should think of upgrading the complete box to a up-to-date distro
with a working security update system anyway, because if you want to keep old
redhat server secure you have at least ten times the work as for a normal
up-to-date system, because there will be no more fixes from redhat for this
kind of system and so you have to patch all own your own :/

our company does linux support; including building custom packages for
otherwise-unsupported RH releases.
(f.ex. we have apt working on RH6.x boxes)

yes, I have newer rsync packages available for this box already. I just need
approval from some other people to install them. I was just asking if
protocol v20 was supported, in case there was some idiotic thing I was
missing in the configuration which would break interoperation with that
protocol.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

from the backuppc documentation for 2.0.2:

If you are using rsync to backup linux/unix machines you should have version
2.5.5 or higher on each client machine. See http://rsync.samba.org. Use
``rsync --version'' to check your version.

so your version seems not to be supported.

--Ralph

Am Donnerstag 03 Juni 2004 21:01 schrieb Carl Wilhelm Soderstrom:
But you should upgrade to a up-to-date version anyway, because there have
been (I think) 2 bugs in rsync that may allow evil hackers to
transfer/delete files that they normaly should not see.

that's only if you're running rsyncd; which we are not. (and do not do
anywhere). but yeah, I know what you mean.

At least for the last problem there is no official redhat patch for this,
because redhat stopped supporting the normal redhat series since 01/2004.

<snip>

P.s.: You should think of upgrading the complete box to a up-to-date
distro with a working security update system anyway, because if you want
to keep old redhat server secure you have at least ten times the work as
for a normal up-to-date system, because there will be no more fixes from
redhat for this kind of system and so you have to patch all own your own
:/

our company does linux support; including building custom packages for
otherwise-unsupported RH releases.
(f.ex. we have apt working on RH6.x boxes)

yes, I have newer rsync packages available for this box already. I just
need approval from some other people to install them. I was just asking if
protocol v20 was supported, in case there was some idiotic thing I was
missing in the configuration which would break interoperation with that
protocol.


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

On 06/03 10:18 , Ralph Pa=DFgang wrote:
from the backuppc documentation for 2.0.2:
=20
If you are using rsync to backup linux/unix machines you should have v=
ersion
2.5.5 or higher on each client machine. See http://rsync.samba.org. Us=
e
``rsync --version'' to check your version.=20
=20
so your version seems not to be supported.

ah.
danke schoen.
I figured there was something obvious I was missing.

--=20
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/