Re: strange limitation on rcmd()
- From: Brian Candler <B.Candler@xxxxxxxxx>
- Date: Mon, 10 Jul 2006 18:50:59 +0100
On Mon, Jul 10, 2006 at 11:47:33AM -0400, Mikhail Teterin wrote:
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...
Well, it's probably worth send-pr'ing it.
I'd first test whether rsh itself forwards stderr properly. Maybe there's
some underlying reason why rcmdsh doesn't have an fd2p argument.
_______________________________________________
freebsd-security@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: strange limitation on rcmd()
- From: Mikhail Teterin
- Re: strange limitation on rcmd()
- References:
- strange limitation on rcmd()
- From: Mikhail Teterin
- Re: strange limitation on rcmd()
- From: Iang
- Re: strange limitation on rcmd()
- From: Simon L. Nielsen
- Re: strange limitation on rcmd()
- From: Mikhail Teterin
- strange limitation on rcmd()
- Prev by Date: Re: strange limitation on rcmd()
- Next by Date: Re: strange limitation on rcmd()
- Previous by thread: Re: strange limitation on rcmd()
- Next by thread: Re: strange limitation on rcmd()
- Index(es):