By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,905 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,905 IT Pros & Developers. It's quick & easy.

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

P: n/a
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.php

Would Fail!

Mar 20 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
be*****@gmail.com wrote:
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

It's a horrible way to build a system. Using a front-controller makes a
large PHP system much more difficult to write.
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?


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.

Mar 20 '06 #2

P: n/a
d
"Colin McKinnon"
<co**********************@ntlworld.deletemeunlessU RaBot.com> wrote in
message news:zg*****************@newsfe5-gui.ntli.net...
be*****@gmail.com wrote:
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

It's a horrible way to build a system. Using a front-controller makes a
large PHP system much more difficult to write.


I'd say that's not entirely true - it is possible for such things to improve
the development of large systems.
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?


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.


He could just rename the php binary somewhere :-P
I suggest you re-examine the problem and see if that is the right
solution.

C.

Mar 21 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.