Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Maarten de Boer
Sorry if this is a silly question, but have you put a shell in your jail? http://tiefighter.et.tudelft.nl/~arthur/cvsd/faq.html#cvsscripts No, I haven't, but why would I? What I execute from loginfo is a standalone application, it should not need a shell at all. Maarten

RE: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Jim.Hyslop
Geoff Beier [mailto:[EMAIL PROTECTED] wrote: Sorry if this is a silly question, but have you put a shell in your jail? OK, here's an even sillier question - what is a chroot jail? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist,

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Geoff Beier
On Fri, 7 Nov 2003 10:05:10 +0100, Maarten de Boer wrote Sorry if this is a silly question, but have you put a shell in your jail? http://tiefighter.et.tudelft.nl/~arthur/cvsd/faq.html#cvsscripts No, I haven't, but why would I? What I execute from loginfo is a standalone application, it

RE: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Schrum, Allan (Allan)
PROTECTED] Subject: Re: Broken pipe with loginfo in a chroot jail Sorry if this is a silly question, but have you put a shell in your jail? http://tiefighter.et.tudelft.nl/~arthur/cvsd/faq.html#cvsscripts No, I haven't, but why would I? What I execute from loginfo is a standalone application

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Maarten de Boer
Notice that the invoking the shell part is not optional. Therefore, to use popen() in a chroot jail (which is required for loginfo) you require a shell. Ah. That would explain a lot... Which shell would that be? /bin/sh? Having a shell in the chroot jail is of course far from ideal.. Is there

RE: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Geoff Beier
On Fri, 7 Nov 2003 09:28:57 -0500 , Jim.Hyslop wrote OK, here's an even sillier question - what is a chroot jail? It's a means of restricting the operations of an application (on UNIX-like systems) to a particular area of a disk. Here's a pretty good explanation:

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Donald Sharp
It's a term to describe what the purpose of chroot is. chroot attempts to severly limit/restrict access to a machine, hence the term 'jail'. donald On Fri, Nov 07, 2003 at 09:28:57AM -0500, Jim.Hyslop wrote: Geoff Beier [mailto:[EMAIL PROTECTED] wrote: Sorry if this is a silly question, but

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Maarten de Boer
Having a shell in the chroot jail is of course far from ideal.. Is there some way aroudn this? Could I use some shell that allows nothing? Okay, I found the answer to this question. If can simply rename the application that I want to run on loginfo to /bin/sh in the chroot jail. That's it! And

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Larry Jones
information X-MTG-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=0, required 5) Cc: [EMAIL PROTECTED] Subject: Re: Broken pipe with loginfo in a chroot jail X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.2 Precedence: list

Re: Broken pipe with loginfo in a chroot jail

2003-11-07 Thread Geoff Beier
On Fri, 7 Nov 2003 15:50:32 +0100, Maarten de Boer wrote Notice that the invoking the shell part is not optional. Therefore, to use popen() in a chroot jail (which is required for loginfo) you require a shell. Ah. That would explain a lot... Which shell would that be? /bin/sh? Having a

Broken pipe with loginfo in a chroot jail

2003-11-06 Thread Maarten de Boer
Hello, I am running a CVS server in a chroot jail, and everything is working okay, apart from one thing. We have been using a commitinfo script for a long time with no problems, and now I wanted to add a loginfo script as well. This however fails with a broken pipe. If I run the same script from

Re: Broken pipe with loginfo in a chroot jail

2003-11-06 Thread Maarten De Boer
The loginfo interface pipes a message into the program spawned by the loginfo file entry, so if your loginfo script ignores its standard input then you'll see this error. My loginfo script (well, not really a script, but an application written in C) does not ignore the standard input: I read

Re: Broken pipe with loginfo in a chroot jail

2003-11-06 Thread Larry Jones
Maarten de Boer writes: I am running a CVS server in a chroot jail, and everything is working okay, apart from one thing. We have been using a commitinfo script for a long time with no problems, and now I wanted to add a loginfo script as well. This however fails with a broken pipe. Most

Re: Broken pipe with loginfo in a chroot jail

2003-11-06 Thread Maarten De Boer
Most likely, the problem is that some command your script uses doesn't exist in your chroot jail -- perhaps even the script's interpreter. I'd It's not a script, it's a small executable - written in c. suggest running CVS with tracing enabled to see if that tells you anything, although I

Re: Broken pipe with loginfo in a chroot jail

2003-11-06 Thread Geoff Beier
On Fri, 7 Nov 2003 00:13:48 + (UTC), Maarten De Boer wrote Most likely, the problem is that some command your script uses doesn't exist in your chroot jail -- perhaps even the script's interpreter. I'd It's not a script, it's a small executable - written in c. Sorry if this is a