|
> Really that should not have been posted! Come on lets not give away all our > secrets. Lets not make it any easier for hackers to learn how to break into > the AS400. I know it is not easy, but how many people really knew where to > look for passwords. Knowing **where** they reside is probably 5% of the problem of actually getting passwords back into clear text. You have the locks on your front door, on your car door, on your suitcases, etc., clearly visible (including more often than not the manufacture of the lock) to the rest of the world but you don't have a problem with them being on display. Neither do I think does IBM, if it was really, really worried about that object being 'found' then they would have made it a non-visible system object long ago... And searching through the MIDRANGE-L archives the object name can be found, also if you look in the API manual, at the error messages returned for some of the security API's the name of the object is in the error message. You can't hide what is already in public view (unless you are Mr. Copperfield) --phil +--- | 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 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.