× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Security by Obscurity vs QADBIFLD
  • From: rob@xxxxxxxxx
  • Date: Thu, 26 Oct 2000 13:52:41 -0500


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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.