How to get networker backup software

2006-06-02 Thread Donald Teed

Hi,

Our institution uses networker for backups.  We absolutely require
networker client for FreeBSD.  I'm astonished that it was just dropped
from ports.

I have a dozen or so machines where networker client is already
humming along and it works well for us.  I have a recently setup
BSD box I want to add to the backup routines.  Unfortunately,
making a tar of nsr folder and copying the networker.sh script
has not worked.  We have the same 4.11 BSD on all BSD boxes.
When I try to run nsrexecd, it dumps core.

I found an old copy of the dists tarball, but that doesn't
contain everything I'm finding in an existing install of networker
client on another BSD box.

Has anyone figured out how to support networker client
since it was dropped from ports?

--Donald
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to get networker backup software

2006-06-02 Thread Donald Teed

As far as I know, the security issues are moot.  The note
I remember seeing said that the default configuration
was problematic.  If our backup server is behind a firewall,
and we always config things after installing, I can't
see how the security issue is relevant enough to rip
it out of ports.  It is far better to have a security issue
awaiting resolution than to have zero backup capability.

The ports skeleton we have is on one machine and
shared by NFS to the rest. It is updated nightly so
the old one is gone.  We do have the tarball
in distfiles, but I don't see a Makefile, etc.

How do I find it from CVS source?  Is there a pointer on
where to find that?

--Donald

On 6/2/06, Randy Pratt [EMAIL PROTECTED] wrote:

On Fri, 2 Jun 2006 16:49:09 -0300
Donald Teed [EMAIL PROTECTED] wrote:

 Hi,

 Our institution uses networker for backups.  We absolutely require
 networker client for FreeBSD.  I'm astonished that it was just dropped
 from ports.

 I have a dozen or so machines where networker client is already
 humming along and it works well for us.  I have a recently setup
 BSD box I want to add to the backup routines.  Unfortunately,
 making a tar of nsr folder and copying the networker.sh script
 has not worked.  We have the same 4.11 BSD on all BSD boxes.
 When I try to run nsrexecd, it dumps core.

 I found an old copy of the dists tarball, but that doesn't
 contain everything I'm finding in an existing install of networker
 client on another BSD box.

 Has anyone figured out how to support networker client
 since it was dropped from ports?

I would think the first thing to do would be to fix the unresolved
security issues.

http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/nwclient/Attic/

http://www.vuxml.org/freebsd/d177d9f9-e317-11d9-8088-00123f0f7307.html

It was marked as forbidden as far back as July 2005 and apparently no
one stepped up to fix those issues and was subsequently removed from
the ports tree. It also seems that the security issues existed as far
back as 2002.

You should be able to copy the ports skeleton(s) from your existing
machines (or get it from CVS) and build it that way.  I'd just be a
bit cautious relying on software with known security issues.

Caveat:  I could be wrong on this since I don't use and have
 never used this port.

HTH,

Randy
--


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


[RESOLVED] Re: How to get networker backup software

2006-06-05 Thread Donald Teed

Hi,

The trick of doing a ports cvsup from back
in time worked.  We have a working networker client again!

I'm even more concerned that the client version
is going to go stale.  I don't know how the package
was made for BSD, and I'm not sure if it
is legally possibly to port the current versions
of the networker client over.

Thanks for the assistance, Randy...

--Donald

On 6/2/06, Randy Pratt [EMAIL PROTECTED] wrote:

On Fri, 2 Jun 2006 19:01:38 -0300
Donald Teed [EMAIL PROTECTED] wrote:

 As far as I know, the security issues are moot.  The note
 I remember seeing said that the default configuration
 was problematic.  If our backup server is behind a firewall,
 and we always config things after installing, I can't
 see how the security issue is relevant enough to rip
 it out of ports.  It is far better to have a security issue
 awaiting resolution than to have zero backup capability.

 The ports skeleton we have is on one machine and
 shared by NFS to the rest. It is updated nightly so
 the old one is gone.  We do have the tarball
 in distfiles, but I don't see a Makefile, etc.

 How do I find it from CVS source?  Is there a pointer on
 where to find that?

You could get a complete tree just before the port was removed by
setting a date in a cvsup file.  Its been awhile since I've done
this but here's a modified example from an old file I still had:

*default host=cvsup4.FreeBSD.org(or whatever)
*default base=/usr/oldtree
*default prefix=/home/oldtree
*default release=cvs
*default delete use-rel-suffix
*default date=2006.03.31.00.00.00
*default compress
ports-all

I think that date is about 8 hours before the ports were removed
from the tree but you might want to check the dates of any other
ports you might need to be sure the date is correct for what you
need.  You can check these with cvsweb:

http://www.freebsd.org/cgi/cvsweb.cgi/

Note that the base and prefix are different so that you don't
clobber your existing ports tree.  Choose something appropriate
for your situation.

Instead of using ports-all, you might save some bandwidth by only
selecting the ports modules you need.  They are listed in:

/usr/share/examples/cvsup/ports-supfile

You would have selected entries in your supfile like:

ports-base
ports-sysutils

After that, just cvsup using the new supfile.  That should get what
is needed and then you'll be able to add them to your NFS tree.

It sounds like you're quite familar with these ports.  Perhaps if
you can get them security patched you might consider becoming the
maintainer for the ports and get them back in the tree.

Perhaps this will get you closer to where you need to be.  If
anyone spots anything I missed, be sure to comment.

Randy

--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]