Re: strange limitation on rcmd()
- From: Mikhail Teterin <mi+kde@xxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Jul 2006 11:47:33 -0400
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
_______________________________________________
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: Brian Candler
- 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
- 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):
Relevant Pages
|
|