RE: ALL I/O in single module was(ARGH!!! (was file open with LR))

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: rob@xxxxxxxxx
> 
> >From a strictly security standpoint I don't see how an I/O module
with a
> firewall trigger improves upon just using the constraints and triggers
> themselves.  Securitywise, what can be done in an I/O module that
couldn't
> be done in the trigger itself?

With an I/O module, it can adopt the authority to update the file, and
thus it becomes the ONLY way to access the file.  You only give the user
the authority to the I/O module, not the file.  Without this capability,
you have to grant authority to the file to the user, which means they
can then use UPDDTA or whatever other means at hand to update the file.

In order to prevent this unauthorized access in a trigger program you'd
have to have a table of users to determine which users can access which
file - in essence you'd have to recreate OS/400 security.

Joe