How to get networker backup software
donald.teed at gmail.com
Fri Jun 2 15:03:08 PDT 2006
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?
On 6/2/06, Randy Pratt <bsd-unix at earthlink.net> wrote:
> On Fri, 2 Jun 2006 16:49:09 -0300
> "Donald Teed" <donald.teed at 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.
> 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.
More information about the freebsd-questions