|
And what would be the workaround(s)? 1-Change the message id for sysreq to not have DSPJOB? Personally I would heave at that. 2-Modify the DSPLIBL command to not have any options, like "5=Display objects in library". This I wouldn't have a problem with at all. 3-Make the purchaser sign a sheet listing suggested security measures regarding user profiles? I know that many of the software products, like Pentasafe, and maybe PowerTools, have options in there to list users who's passwords match their user profiles. List weak passwords (ones the packages easily hacked themselves). And so on. If the purchaser decides to not take advantage of any of these packages after being made aware - then don't come crying. This option would be too tough of a sell. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
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
