RE: ODBC Security

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Change public authority.  Have your application run under owner authority
and the owner has access to update the files.  Generally you create one
entry point security program to see if that person has access to the program
they are trying to run.  This adopts owner authority for the job.  Be
careful not to give users a command line while this program is active.


Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Quazy [mailto:quazy@SoftHome.net]
Sent: Thursday, November 09, 2000 9:26 AM
To: midrange-l@midrange.com
Subject: ODBC Security


How does everyone deal with security on the 400 and the ability to use ODBC?

If production files are set to public authority to *change, what can I 
do.  users don't have access to manipulate the data from the AS/400 (I have 
taken all those ways away).  But even if a user with basically no authority 
gets on through ODBC they could do anything they want to the database.


What is there you can do?
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---