Vpn configurations are so often poorly chosen and we should not let critical infrastructure run on outdated IPsec for instance.
It may seem natural to build such infrastructure for a life span of 20-30 years but do you remember what state of the art was back in 2001? Most of that is now basically considered broken. Software is living and should never be « set-and-forget »
"- there are no transcription errors or mutations in a correct copy routine."
You only know it's correct after you verify the fact so formally that should read ...correct copy and verify routine.
Incidentally, we used to have switches to verify after copy such as /v but programming sloppiness and impatience - in having to wait extra time for the verify - has meant that the entropy for data processing integrity has increase as a consequence.
Right, no one seems to give a damn about such matters these days.
Even if you had bug-free hardware and formally verified software, your cryptography is broken and your kit has side channel issues that were never dreamed of 20 years ago.
I should clarify: I'm talking about software related to security. I'm sure you wouldn't want to use outdated broken crypto just because libraries already exist for it, for example.
It may seem natural to build such infrastructure for a life span of 20-30 years but do you remember what state of the art was back in 2001? Most of that is now basically considered broken. Software is living and should never be « set-and-forget »