Security by Obscurity vs QADBIFLD

[rob@xxxxxxxxx]

You know that if you do a WRKOBJ LIB/OBJ and you do not have access to that
object it won't appear in the list, right?  And you know that if you do a
DSPOBJD LIB/OBJ objtype you'll get a message that you are not authorized to
that object right?  The first is security by obscurity.  Bit a chap here
who had a secured file in the library list higher than an unsecured object.

We all know that security by obscurity is a joke method anyways, right?
Clever people always figure things out anyways and you need to use real
security.

While knowing that, does anyone still find it slightly unsettling that the
access to QSYS/QADBIFLD is *PUBLIC *CHANGE?  Think of the SQL statement:
SELECT * FROM qadbifld WHERE
(ucase(DBITXT) like '%PAY%' and
 ucase(DBITXT) like '%RATE%')


Rob Berendt

==================
Remember the Cole!

+---
| 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
+---