Martin,
Not true. Using UOlogin, I could run a filter and only allow a
subset of the valid user list access. That would stop people from using
telnet ids as UO ids. If you expand this to lock out some accounts to
ALL UO logins, you can draw a box around the UO user.
Now, if you said 'great ideas but they take too much work' then I'd
be inclined to agree with you. We need a simpler way.
- Chuck "Simple" Barouch
Martin Phillips wrote:
These are all great ideas but they still do not address the
fundamental problem.... A user who can validly make a connection to
use an application can write his own client program to subvert the
system. None of the proposed solutions solve this. As far as we can
see, it requires a change to the server side of Uniobjects (hence the
solution to the equivalent functions in our product).
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
