On Wed, Jan 10, 2001 at 09:31:21PM -0500, D-Man wrote:
...
> I recall seeing somewhere that with the new interpreter, .pyo files
> can be executed (by the interpreter, but by calling the file not the
> interpreter). Maybe not. I wish I could remember where I saw
> that.
It doesn't work here wit
On Wed, Jan 10, 2001 at 09:31:21PM -0500, D-Man wrote:
> I recall seeing somewhere that with the new interpreter, .pyo files
> can be executed (by the interpreter, but by calling the file not the
> interpreter). Maybe not. I wish I could remember where I saw
> that.
I doubt it. My understandin
On Thu, Jan 11, 2001 at 01:47:14AM +0100, Carel Fellinger wrote:
| On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote:
| > On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote:
| > | would writing scripts in a compiled language like
| > | C be a solution?
| > |
| >
| > If any binary files c
On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote:
> On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote:
> | would writing scripts in a compiled language like
> | C be a solution?
> |
>
> If any binary files can be exec as suid, then I would recommend
> python. It will have more of the
On Wed, Jan 10, 2001 at 10:42:22AM -0800, brian moore wrote:
> On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote:
> > sorry for off-topic, but I've been banging my head trying to set up shell
> > scripts that can be executed but not read by a user.
>
> Not doable.
>
> The shell needs to read
On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote:
> sorry for off-topic, but I've been banging my head trying to set up shell
> scripts that can be executed but not read by a user.
>
> Basically, for test.sh :
>
> #!/usr/bin/bash
> echo hullo!
>
> ***
> [EMAIL PROTECTED]:~]$ chmod 111 test
On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote:
> On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote:
> | would writing scripts in a compiled language like
> | C be a solution?
> |
>
Errm .. then they are not scripts anymore...
Cliff
> If any binary files can be exec as suid, then I
On Mon 10 Jan 00, 4:04 AM, D-Man said...
> On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote:
> | would writing scripts in a compiled language like
> | C be a solution?
> |
>
> If any binary files can be exec as suid, then I would recommend
> python. It will have more of the feel of a scr
On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote:
| would writing scripts in a compiled language like
| C be a solution?
|
If any binary files can be exec as suid, then I would recommend
python. It will have more of the feel of a script with its high level
view of things.
Python programs
would writing scripts in a compiled language like
C be a solution?
can a user have permission to exec a script
contained in a directory they don't have read
access to?
xucaen
--- Rick <[EMAIL PROTECTED]> wrote:
> that is what I was afraid of. I'd given some
> thought to sudo or suid but
> may
that is what I was afraid of. I'd given some thought to sudo or suid but
maybe letting users read the script is okay. So much for security through
obscurity ;)
thanks again
rick
brian moore writes:
> On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote:
> > sorry for off-topic, but I've been b
On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote:
> sorry for off-topic, but I've been banging my head trying to set up shell
> scripts that can be executed but not read by a user.
Not doable.
The shell needs to read them in order to execute them.
(Well, you could do something REALLY evil
Rick wrote:
>
> sorry for off-topic, but I've been banging my head trying to set up shell
> scripts that can be executed but not read by a user.
>
> Basically, for test.sh :
>
> #!/usr/bin/bash
> echo hullo!
>
> ***
> [EMAIL PROTECTED]:~]$ chmod 111 test.sh
> [EMAIL PROTECTED]:~]$ ./test.sh
> .
13 matches
Mail list logo
