Date: Mon, 10 Jul 2006 11:47:33 -0400 From: Mikhail Teterin <mi+kde@aldan.algebra.com> To: "Simon L. Nielsen" <simon@freebsd.org>, Brian Candler <B.Candler@pobox.com> Cc: Brian Candler <B.Candler@pobox.com>, Mikhail Teterin <mi+mx@aldan.algebra.com>, freebsd-security@freebsd.org, net@freebsd.org, imp@freebsd.org, Iang <iang@iang.org> Subject: Re: strange limitation on rcmd() Message-ID: <200607101147.34530@aldan> In-Reply-To: <20060710141729.GF1101@zaphod.nitro.dk> References: <200607072030.01999.mi%2Bmx@aldan.algebra.com> <44B25F0A.5040709@iang.org> <20060710141729.GF1101@zaphod.nitro.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 10 July 2006 10:17, Simon L. Nielsen wrote: = Actually it is, but it would obviously be a stupid idea to do so any = place where privileged ports are required... It would be. But where they are NOT required, it is stupid to check the geteuid() inside the client's rcmd :-) Thank you very much for your explanation, Brian, rsh being an SUID is something I overlooked. What I remain upset about, though, is that the rcmdsh(), which is used by rcmd() ignores the fd2p parameter making it impossible to capture the remote's stderr... Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607101147.34530>