Groups > alt.folklore.computers > #212530

Re: Early mainframe security

From	Anne & Lynn Wheeler <lynn@garlic.com>
Newsgroups	alt.folklore.computers
Subject	Re: Early mainframe security
Date	2020-08-03 12:25 -1000
Organization	Wheeler&Wheeler
Message-ID	<87tuxjnz7v.fsf@localhost> (permalink)
References	<rddjkg$ffe$1@z-news.wcss.wroc.pl>

Show all headers | View raw

Within a year of taking two semester hr intro to computers/fortran, I
was hired fulltime by the univ to be responsible for mainframe
systems. Last week some of the people came out from the science center
to install CP67. I rewrote lot of the code and sometimes IBM would
suggest things to rewrite ... in retrospect, some of the suggestions
could have originated with gov. agencies ... I didn't learn about these
guys until much later (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

When I graduate, I join the science center. The science center had
ported APL\360 to CP67/CMS as CMS\APL ... had to redo the storage
management and garbage collection for large demand page virtual memory
... also added API to systems services (like file read/write)
... enabling lots of real-world applications.

One of the remote online CMS\APL early users were the business planners
in Armonk corporate hdqtrs that installed the most holiest of corporate
assets on the cambridge system (detailed customer information) to do
business modeling. We had to demonstrate a very high level of security
since the system also had profs, staff, and students online users from
some of the univ. in the boston/cambridge area.

Then company got a new CSO that had come from gov. service (at one time
head of presidential detail) and I got asked to run around with him and
talk about computer security (while a little bit of physical security
rubs off on me).

there is MVS folklore about one of the agencies looking at installing
MVS ... but before they wanted the "exact" source for all the components
they would be running (for review). Company spent $5M investigating the
problem before deciding that it was practical.

--
virtualization experience starting Jan1968, online at home since Mar1970

Thread

Early mainframe security antispam@math.uni.wroc.pl - 2020-06-29 20:40 +0000
  Re: Early mainframe security Peter Flass <peter_flass@yahoo.com> - 2020-06-29 13:49 -0700
  Re: Early mainframe security Dan Espen <dan1espen@gmail.com> - 2020-06-29 16:53 -0400
    Re: Early mainframe security antispam@math.uni.wroc.pl - 2020-06-29 23:59 +0000
      Re: Early mainframe security Peter Flass <peter_flass@yahoo.com> - 2020-06-29 17:24 -0700
        Re: Early mainframe security Thomas Koenig <tkoenig@netcologne.de> - 2020-06-30 07:57 +0000
        Re: Early mainframe security "Kerr-Mudd,John" <notsaying@invalid.org> - 2020-06-30 08:21 +0000
  Re: Early mainframe security Douglas Miller <durgadas311@gmail.com> - 2020-06-29 13:55 -0700
    Re: Early mainframe security J. Clarke <jclarke.873638@gmail.com> - 2020-06-29 17:40 -0400
    Re: Early mainframe security scott@slp53.sl.home (Scott Lurndal) - 2020-06-30 00:08 +0000
      Re: Early mainframe security timcaffrey420@gmail.com - 2020-07-01 07:38 -0700
        Re: Early mainframe security scott@slp53.sl.home (Scott Lurndal) - 2020-07-01 15:14 +0000
          Re: Early mainframe security timcaffrey420@gmail.com - 2020-07-01 13:03 -0700
            Re: Early mainframe security scott@slp53.sl.home (Scott Lurndal) - 2020-07-02 00:52 +0000
              Re: Early mainframe security timcaffrey420@gmail.com - 2020-07-11 18:04 -0700
                Re: Early mainframe security Grant Taylor <gtaylor@tnetconsulting.net> - 2020-07-11 19:10 -0600
                Re: Early mainframe security John Levine <johnl@taugh.com> - 2020-07-12 02:50 +0000
                Re: Early mainframe security timcaffrey420@gmail.com - 2020-07-13 14:26 -0700
  Re: Early mainframe security David Wade <g4ugm@dave.invalid> - 2020-06-29 23:00 +0100
    Re: Early mainframe security antispam@math.uni.wroc.pl - 2020-06-30 00:27 +0000
      Re: Early mainframe security and channel programs John Levine <johnl@taugh.com> - 2020-06-30 02:58 +0000
      Re: Early mainframe security David Wade <g4ugm@dave.invalid> - 2020-06-30 11:34 +0100
      Re: Early mainframe security Peter Flass <peter_flass@yahoo.com> - 2020-06-30 06:15 -0700
        Re: Early mainframe security antispam@math.uni.wroc.pl - 2020-06-30 14:01 +0000
          Re: Early mainframe security David Wade <g4ugm@dave.invalid> - 2020-06-30 22:39 +0100
      Re: Early mainframe security Jon Elson <elson@pico-systems.com> - 2020-06-30 19:37 -0500
  Re: Early mainframe security John Levine <johnl@taugh.com> - 2020-06-29 22:18 +0000
    Re: Early mainframe security Peter Flass <peter_flass@yahoo.com> - 2020-06-29 15:49 -0700
    Re: Early mainframe security Grant Taylor <gtaylor@tnetconsulting.net> - 2020-06-29 18:28 -0600
      Re: Early mainframe security Quadibloc <jsavard@ecn.ab.ca> - 2020-06-29 21:11 -0700
      Re: Early mainframe security David Wade <g4ugm@dave.invalid> - 2020-06-30 11:35 +0100
        Re: Early mainframe security Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-30 22:18 +0000
          Re: Early mainframe security scott@slp53.sl.home (Scott Lurndal) - 2020-07-01 15:08 +0000
    Re: Early mainframe security Thomas Koenig <tkoenig@netcologne.de> - 2020-06-30 07:51 +0000
      Re: Early mainframe security Bob Eager <news0073@eager.cx> - 2020-06-30 08:49 +0000
  Re: Early mainframe security Ahem A Rivet's Shot <steveo@eircom.net> - 2020-06-30 09:43 +0100
  Re: Early mainframe security Jon Elson <elson@pico-systems.com> - 2020-06-30 19:23 -0500
    Re: Early mainframe security Peter Flass <peter_flass@yahoo.com> - 2020-06-30 18:03 -0700
      Re: Early mainframe security J. Clarke <jclarke.873638@gmail.com> - 2020-06-30 22:32 -0400
        Re: Early mainframe security John Levine <johnl@taugh.com> - 2020-07-01 03:21 +0000
          Re: Early mainframe security J. Clarke <jclarke.873638@gmail.com> - 2020-06-30 23:52 -0400
          Re: Early mainframe security Dan Espen <dan1espen@gmail.com> - 2020-06-30 23:56 -0400
      Re: Early mainframe security Jon Elson <elson@pico-systems.com> - 2020-07-01 22:21 -0500
  Re: Early mainframe security timcaffrey420@gmail.com - 2020-07-01 07:33 -0700
  Re: Early mainframe security Anne & Lynn Wheeler <lynn@garlic.com> - 2020-08-03 12:25 -1000
    Re: Early mainframe security Anne & Lynn Wheeler <lynn@garlic.com> - 2020-08-03 12:58 -1000

csiph-web