|
On Fri, 2002-01-04 at 16:25, rob@dekko.com wrote: > > This sounds like an attempt at security by obscurity. If you don't let > people know what libraries, files and fields are on the system then they > won't try so hard to hack into others data. > > It is my understanding that IBM put this file on the system for use in > Client/Server applications (remember those?) Attempts to tighten down this > file may have implications unless IBM worked around and has some adopted > method for C/S to get pertinent information from this file. > > Rob Berendt Rob ISTR seeing something about files in QSYS2 as the ones to use, rather than those in QSYS - probably in a discussion here - but I don't recall any more details. We're still on V4R4, & QSECURITY(30) so I had assumed that the tightening up was due to a later release/enhanced security rather than a site imposed policy. Regards, Martin -- martin@dbg400.net / jamaro@firstlinux.net http://www.dbg400.net DBG/400 - DataBase Generation utilities Open Source test environment tools for the AS/400 / iSeries and miscellaneous database & spooled file management commands.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
