From: cross@spitfire.i.gajendra.net   
      
   In article <10mlbpo$1ohf1$1@dont-email.me>,   
   Stephen Hoffman   wrote:   
   >On 2026-02-12 12:40:56 +0000, gcalliet said:   
   >> And as usual, the issue is between the "must" and the "can".   
   >   
   >Rock versus Hard Place.   
   >   
   >If you can't maintain your tools, you're headed for increasing costs   
   >and increasing trouble.   
      
   It's always interesting how those policies designed to increase   
   stability tend to degrade it over time.  Excessive caution about   
   upgrades and ongoing maintenance of software environments is the   
   clear cause of many problems.   
      
   I get regulatory issues and so on, and that "IT" is an immature   
   field with widely varying adherence to best practices.  But   
   progress has been made, while much in the way of policy was   
   written in an earlier time, and written to the lowest common   
   denominator.   
      
   >[snip]   
   >Here? Bastion hosts, network isolation, ongoing network scans for   
   >shenanigans. And plans for and budgets for maintenance and upgrades.   
   >Otherwise,  the scheduled downtime becomes unscheduled downtime.   
      
      
   Yup.  Logging and auditing, too.   
      
   	- Dan C.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)