Kernel.php ??? Limit all execution to this...

[bellefy@gmail.com]

Hi All,

I have, what I'd like to think as anyway, a unique situation.

I have a client that has contracted me to build a custom inventory
management system to be installed at the client's location. More
specifically, a custom reporting display system through a kiosk-like
linux installation using a locked-down FireFox.

My development style has always been centralized around one primary
class file (Kernel.php) that calls in the appropriate modules as
needed.

For example:
$ php ./Kernel.php sendReport

Because this job is to be installed at the client location, is there a
way that I can limit the entire installation of PHP to only allow
Kernel.php to execute?

In other words, I want to be able to completely lock down PHP to stop
any prying eyes from being able to execute ANY other PHP scripts on the
reporting machine.

So...
$ php ./someOtherFile.p hp

Would Fail!

[Colin McKinnon]

Re: Kernel.php ??? Limit all execution to this...

bellefy@gmail.c om wrote:
[color=blue]
> I have, what I'd like to think as anyway, a unique situation.
>
> I have a client that has contracted me to build a custom inventory
> management system to be installed at the client's location. More
> specifically, a custom reporting display system through a kiosk-like
> linux installation using a locked-down FireFox.
>
> My development style has always been centralized around one primary
> class file (Kernel.php) that calls in the appropriate modules as
> needed.
>
> For example:
> $ php ./Kernel.php sendReport
>[/color]

It's a horrible way to build a system. Using a front-controller makes a
large PHP system much more difficult to write.
[color=blue]
> Because this job is to be installed at the client location, is there a
> way that I can limit the entire installation of PHP to only allow
> Kernel.php to execute?
>[/color]

If that is really your objective then the shortest route to that goal would
be to rewrite the PHP or hack something terrible using an access control
system like RBACS.

I suggest you re-examine the problem and see if that is the right solution.

C.

[d]

Re: Kernel.php ??? Limit all execution to this...

"Colin McKinnon"
<colin.thisisno tmysurname@ntlw orld.deletemeun lessURaBot.com> wrote in
message news:zgFTf.2856 $H%3.1521@newsf e5-gui.ntli.net...[color=blue]
> bellefy@gmail.c om wrote:
>[color=green]
>> I have, what I'd like to think as anyway, a unique situation.
>>
>> I have a client that has contracted me to build a custom inventory
>> management system to be installed at the client's location. More
>> specifically, a custom reporting display system through a kiosk-like
>> linux installation using a locked-down FireFox.
>>
>> My development style has always been centralized around one primary
>> class file (Kernel.php) that calls in the appropriate modules as
>> needed.
>>
>> For example:
>> $ php ./Kernel.php sendReport
>>[/color]
>
> It's a horrible way to build a system. Using a front-controller makes a
> large PHP system much more difficult to write.[/color]

I'd say that's not entirely true - it is possible for such things to improve
the development of large systems.
[color=blue][color=green]
>> Because this job is to be installed at the client location, is there a
>> way that I can limit the entire installation of PHP to only allow
>> Kernel.php to execute?
>>[/color]
>
> If that is really your objective then the shortest route to that goal
> would
> be to rewrite the PHP or hack something terrible using an access control
> system like RBACS.[/color]

He could just rename the php binary somewhere :-P
[color=blue]
> I suggest you re-examine the problem and see if that is the right
> solution.
>
> C.
>[/color]