From owner-freebsd-security Tue Jan 11 12:31:56 2000 Delivered-To: freebsd-security@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id ABAF914C14 for ; Tue, 11 Jan 2000 12:31:48 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA03435 for freebsd-security@freebsd.org; Tue, 11 Jan 2000 21:31:47 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id UAA61875 for freebsd-security@freebsd.org; Tue, 11 Jan 2000 20:16:10 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: UUCP over SSH tunnel? Date: 11 Jan 2000 20:16:10 +0100 Message-ID: <85fvhq$1sda$1@bigeye.rhein-neckar.de> References: <20000111040509.A17467@theatre.sax.de> <200001111256.JAA18889@ns1.via-net-works.net.ar> To: freebsd-security@freebsd.org Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Fernando Schapachnik wrote: > Then create an account on your server that has, say, /bin/cat as shell, > and make sure you limit the resources it can consume (to limit any DoS > possibility). If you have control over the server, you can just give the account /usr/libexec/uucp/uucico as shell and run uucp over a pipe port that does "ssh -l login host". -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message