Hey John: To have some one get you, i.e.; overlay your storage if you are in Key 0, they have to be in Key 0 and right PSW correct ?
Scott J Ford Software Engineer http://www.identityforge.com/ ________________________________ From: John McKown <[email protected]> To: [email protected] Sent: Friday, April 12, 2013 3:23 PM Subject: Re: Storage and Tokens Technically, not "write protected" storage per se, but key 0 storage. Which does make them write protected from most users. On Fri, Apr 12, 2013 at 1:42 PM, Gerhard Postpischil <[email protected]> wrote: > On 4/12/2013 11:55 AM, John Gilmore wrote: >> >> Richard Peurifoy has been lucky, and perhaps others have been too, but >> the basic difficulty remains. The use of these fields is >> undocumented, in fact unpoliced, and thus also unwise. > > > As a long-time user of both CVTUSER and TCBUSER, > I have to disagree. These fields are in write-protected storage, giving > the installation absolute control over their use. > > Some years ago, prior to IBM's adoption of the vendor table, I went to a > conference. During my absence the local CA salesman, who happened to be > golfing with the company president, talked him into doing performance > measurement on our MVS system. One of my systems people installed their > software; nobody noticed that we were no longer collecting accounting > data, or printing billing information on the jobs. Since then I place > eye-catchers in control blocks, and check for their presence. Some > diligence after installing new software suffices to keep things safe. > > We had no problems with vendor software after the vendor table was > introduced, and the only conflicts remaining tend to come from some CBT > and similar software, most of which offers source, so can be checked. > > I'm not sure where luck comes into this. > > Gerhard Postpischil > Bradford, Vermont -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
