How about using file level security, and common area in your subroutines.
Marc Harbeson ERP/Systems Administrator Brinly Hardy Company O - (812) 218-7206 F - (812) 218-6084 [EMAIL PROTECTED] www.brinly.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Friday, May 27, 2005 2:03 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Uniobjects hack Steve, thanks for that jak ----- Original Message ----- From: "Steve Johnson" <[EMAIL PROTECTED]> To: <u2-users@listserver.u2ug.org>; "U2UG" <u2-users@listserver.u2ug.org> Sent: Friday, May 27, 2005 2:46 PM Subject: Re: [U2] Uniobjects hack > How about running a "monitor" program constantly in the > background. It monitors all new logins to U2. The new login > process must send a "sleeping pill" to the monitor within a > short time after login -- "short" being relative to your > system performance. If the monitor doesn't receive this > "sleeping pill" then it kills the new login. The trick here is > to keep the requirement for this "sleeping pill" as secret as > possible; and to invent one that cannot be easily spoofed; and > to insure that the monitor is always active. > > Steve Johnson > FXA Group Ltd > Bangkok > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
