[Info-vax] What to do with my VAX.....

[seasoned_geek]

On Monday, November 2, 2020 at 4:08:04 AM UTC-6, Alexander Schreiber wrote:
> seasoned_geek <rol... at logikalsolutions.com> wrote: 
> > On Saturday, October 17, 2020 at 9:10:35 AM UTC-5, Bill Gunshannon wrote: 

> > There is absolutely no way of securing any system using *nix based 
> > TCP/IP when it is connected to the Internet.
> That is, to say it politely, utter nonsense. Yes, securing a network service 
> is a non-trivial exercise, because it requires more than just grabbing 
> random code from the Internet, nailing it together and calling it done 
> (e.g. the NodeJs and friends approach). You need to actually understand 
> what your are trying to achieve, what you are doing, pay attention to 
> security starting at the design stage and be competent. If you can't 
> measure up to this, you have no business building network services. 
> 
> That is entirely doable and being demonstrated on a daily basis.

You mean they are breached on a daily basis. So often in fact they hardly make the news unless they set a new identity theft record.

> > Lots of places dusting off 
> > old proprietary protocols for internal networks, putting one or two 
> > sacrificial machines out on the Internet and only installing/allowing 
> > the proprietary protocol between them and the internal network.
> Well, there are clueless idiots in charge everywhere: 
> - Shannons Maxim applies ("The enemy knows the system.") 
> - proprietary protocols means fewer people have looked at the design 
> and implementation, it's less widely used, less stress tested and 
> most likely has bugs that more commonly used services fixed ages 
> ago 

Like the Bash security breach exploited for ~25 years before being outted in public?