Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.folklore.computers > #212178

Re: Early mainframe security

From John Levine <johnl@taugh.com>
Newsgroups alt.folklore.computers
Subject Re: Early mainframe security
Date 2020-07-01 03:21 +0000
Organization Taughannock Networks
Message-ID <rdgvf9$uo2$1@gal.iecc.com> (permalink)
References <rddjkg$ffe$1@z-news.wcss.wroc.pl> <NZednXNvgccVSmbDnZ2dnUU7-WfNnZ2d@giganews.com> <1733854713.615258045.554720.peter_flass-yahoo.com@news.eternal-september.org> <hbtnfflqu2nqedirnhhs30vh9ouu9ioa5k@4ax.com>

Show all headers | View raw


In article <hbtnfflqu2nqedirnhhs30vh9ouu9ioa5k@4ax.com>,
J. Clarke  <jclarke.873638@gmail.com> wrote:
>>How much of a problem was this when the system was designed? Work on the
>>360 goes back to the start of the 60s, if not back to the 50s. In those
>>days computers were locked away and only staff had access, so I don’t think
>>there were hackers. by 64 it was more of a problem.
>
>For certain values.  A crooked employee would still be a problem, just
>easier to catch and less likely to get away with it.

A crooked employee didn't need operating system security bugs. I'd
think they'd do things like drop a few fake cards into the nightly
accounting update run.


-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

Back to alt.folklore.computers | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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