There have been vulnerabilities in some of the protocols. That said, the community has been fairly good about fixing them.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of zMan <zedgarhoo...@gmail.com> Sent: Monday, January 13, 2020 11:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What is a mainframe? Eh? That's silly. There's nothing inherent about TCP/IP that makes things hackable. Any connectivity creates potential exposures, whether it's TCP/IP, SNA, bisync... On Sat, Jan 11, 2020 at 3:53 PM z/OS scheduler <z.sch...@gmail.com> wrote: > Welll, in my opinion the mainframe died when IBM allowed tcpip on their > servers. From that point onwards it just became another server that could > be hacked via TCPIP ports. > > James O'Leary > > Op vr 10 jan. 2020 om 21:05 schreef Steve Smith <sasd...@gmail.com>: > > > Well, it is Friday: https://www.youtube.com/watch?v=d0-pLcgq-2M > > > > It's also about a bank :-) > > > > -- > > sas > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- zMan -- "I've got a mainframe and I'm not afraid to use it" ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
