Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Jun 2006 16:43:09 -0400
From:      Randy Pratt <bsd-unix@earthlink.net>
To:        "Donald Teed" <donald.teed@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: How to get networker backup software
Message-ID:  <20060602164309.9863f9d8.bsd-unix@earthlink.net>
In-Reply-To: <dd4da0390606021249m58bfbb16m8f391d3373e90024@mail.gmail.com>
References:  <dd4da0390606021249m58bfbb16m8f391d3373e90024@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2 Jun 2006 16:49:09 -0300
"Donald Teed" <donald.teed@gmail.com> 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
-- 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060602164309.9863f9d8.bsd-unix>