Before 370 virtual memory was announced, a copy of internal document leaked to industry magazine. There was then a "Pentagon Papers" like investigation to find the leaker. Also all company copiers were retrofitted that placed a machine identification on all copied pages. Then for the "Future System" project http://www.jfsowa.com/computer/memo125.htm
they decided to deploy only softcopy versions of the FS documents on specially modified VM370/CMS systems, which could only be read/accessed from specific 3270 terminals. I was in the process of moving a lot of my enhancements from CP67 to VM370 and had some weekend time on a 370 system in a machine room that had one of the modified FS document systems. I went in late Friday afternoon to double check everything was ready for me coming in over the weekend. They started needling me that even if I was left alone in the machine room all weekend, I wouldn't be able to access FS documents in their enhanced VM370 sysem. Finally it got too much, and I asked them to log off all users and disable logins from outside the machine room. From the front panel, I flipped a bit in kernel storage, which had the effect of accepting anything typed as valid password. I then gave them a list of countermeasures that would be required to block skilled attacker (including encrypted files). Other tivia ... gone 404, but lives on at wayback machine. http://web.archive.org/web/20090117083033/http://www.nsa.gov/research/selinux/list-archive/0409/8362.shtml -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
