Date: Tue, 27 Nov 2001 13:47:42 -0500 (EST) From: Mitch Collinsworth <mitch@ccmr.cornell.edu> To: Adam Laurie <adam@algroup.co.uk> Cc: Tom Beer <mailings@analogon.com>, security@FreeBSD.ORG Subject: Re: Amanda - inetd Message-ID: <Pine.LNX.4.10.10111271344530.988-100000@ruby.ccmr.cornell.edu> In-Reply-To: <3C03D8EF.58AF9BF9@algroup.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Nov 2001, Adam Laurie wrote: > Tom Beer wrote: > > > > I'm planning to install amanda (remote backup > > solution) on a freebsd box as a client. Unfourtunately > > amanda needs inetd, which I don't want to start > > for security reasons. Even not tcpwarrped. > > Is there a way to bring my ppp dialup connection > > down, start inetd, start amanda, ending inetd after > > the backup and starting my ppp connection > > again? Or is there a better solution? > > use xinetd and bind amanda's service only to loopback. oh, and make sure > your loopback is protected against remote routing. ipfw in "open" mode > will do this if you're not already running a firewall anyway. He said amanda client. This means an amanda server will come calling to initiate the client's backups. This means the amanda port on the client needs to be accessible to the amanda server. Your solution is not 'better', it's 'nonsense'. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10111271344530.988-100000>