And a new car today also probably won't be rusted in less than 10 years time, what exactly is your point?
>Nobody will blame you for bad crypto if you released software in [the 80s and early 90s].
So you are 100% agreeing with me.
Security expert Bruce Schneier expanded upon what I said back in 1998:
>Cryptographic algorithms have a way of degrading over time. It's a situation that most techies aren't used to: Compression algorithms don't compress less as the years go by, and sorting algorithms don't sort slower. But encryption algorithms get easier to break; something that sufficed three years ago might not today.
>Several things are going on. First, there's Moore's law. Computers are getting faster, better networked, and more plentiful... Cryptographic algorithms are all vulnerable to brute force--trying every possible encryption key, systematically searching for hash-function collisions, factoring the large composite number, and so forth--and brute force gets easier with time. A 56-bit key was long enough in the mid-1970s; today that can be pitifully small. In 1977, Martin Gardner wrote that 129-digit numbers would never be factored; in 1994, one was.
>Aside from brute force, cryptographic algorithms can be attacked with more subtle (and more powerful) techniques. In the early 1990s, the academic community discovered differential and linear cryptanalysis, and many symmetric encryption algorithms were broken. Similarly, the factoring community discovered the number-field sieve, which affected the security of public-key cryptosystems.
https://www.schneier.com/essays/archives/1998/05/the_crypto_...
The ironic thing is this article also said "I recommend SHA-1"... SHA-1 was broken 7 years later.