on 5/31/2000 1:42 AM, Chris Kimpton at [EMAIL PROTECTED] wrote:
> I was just thinking (I know, always dangerous...)
>
> Given the nature of a call to the Turbine servlet, someone could mix and match
> the action screen calls maliciously - .../action/ResetDB/screen/HomePage
>
> I guess that the login/permissions process should limit to some extent what
> can be done - but for the cases that still get through, I presume the actions
> need to be fairly defensive to ensure that the screens get called in the
> correct way - although in some ways you don't want to be too prescriptive, as
> this limits the power of the model.
>
> Any comments on whats been done to date regarding this kind of thing? Or am I
> worrying about nothing?
you are essentially worrying about something that isn't new. you should
ALWAYS have defensive programming in your code to check the input to see if
it is what you are expecting. you should not let the action execute unless
you have the fields and values that you expect. the same thing could happen
for ANY web app. if you use the ActionEvent model, it makes it MUCH easier
to write little methods that handle each form submission and thus simplified
form checking.
one good example is: my current favorite way to screw up other people's
websites is to put negative values for integers. :-)
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
