Live data from Hacker News

How Frogger 2’s source code was recovered from a destroyed tape [video]

youtube.com

11–20 of 78 posts

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#11
post #4

A lot of work, but with success as reward! Makes you wonder how easy or difficult it will be in 30 years to 'recover' data from today.

Hard, but it depends on backup / duplication strategies; this is why e.g. the internet archive is so important, and I hope there are multiple parties doing the same thing for redundancy.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#12
post #9
post #8

Earlier quoted context omitted.

> Encryption for 30 years ago? Trivially breakable with quantum I wouldn't be so sure - quantum computers aren't nearly as effective for symmetric algorithms as they are for pre-quantum asymmetric algorithms.

Regardless of the parent's statement, just normal compute in 30 years, plus general vulnerabilities and weaknesses discovered, will ensure that anything encrypted today is easily readable in the future. I can't think of anything from 30 years ago that isn't just a joke today. The same will likely be true by 2050, quantum computing or not. I wonder how many people realise this? Even if one disagrees with my certainty,…

>normal compute

You are underestimating the exponential possibilities of keys.

>plus general vulnerabilities and weaknesses discovered, will ensure that anything encrypted today is easily readable in the future.

You can't just assume that there is always going to be new vulnerabilities that cause it to be broken. It ignores that people have improved at designing secure cryptography over time.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#13
post #9
post #8

Earlier quoted context omitted.

> Encryption for 30 years ago? Trivially breakable with quantum I wouldn't be so sure - quantum computers aren't nearly as effective for symmetric algorithms as they are for pre-quantum asymmetric algorithms.

Regardless of the parent's statement, just normal compute in 30 years, plus general vulnerabilities and weaknesses discovered, will ensure that anything encrypted today is easily readable in the future. I can't think of anything from 30 years ago that isn't just a joke today. The same will likely be true by 2050, quantum computing or not. I wonder how many people realise this? Even if one disagrees with my certainty,…

> I can't think of anything from 30 years ago that isn't just a joke today.

AES is only 3 years shy of 30.

If you used MD5 as a keystream generator I believe that would still be secure and that's 33 years old.

3DES is still pretty secure, isn't it? That's 44 years old.

As for today's data, there's always risk into the future but we've gotten better as making secure algorithms over time and avoiding quantum attacks seems to mostly be a matter of doubling key length. I'd worry more about plain old leaks.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#14
post #7
post #6

Earlier quoted context omitted.

> Makes you wonder how easy or difficult it will be in 30 years to 'recover' data from today. The challenges will be different. Flash loses its charge in 30 years, most disks are encrypted, and on-site physical backups are mostly a thing of the past. The source might survive in a cloud repo, but it'll either be tied up for legal reasons or deleted when the customer stops paying the bill. But storage is cheap and gett…

Easy. The “deleted” even overwritten data can leave ghosts even multiple layers deep (think of a clay tablet or painting with multiple inscriptions) Encryption for 30 years ago? Trivially breakable with quantum

Has this been proven for flash storage? Once a flash charge is depleted its gone forever, its not like magnetic storage of old.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#16
post #7
post #6

Earlier quoted context omitted.

> Makes you wonder how easy or difficult it will be in 30 years to 'recover' data from today. The challenges will be different. Flash loses its charge in 30 years, most disks are encrypted, and on-site physical backups are mostly a thing of the past. The source might survive in a cloud repo, but it'll either be tied up for legal reasons or deleted when the customer stops paying the bill. But storage is cheap and gett…

Easy. The “deleted” even overwritten data can leave ghosts even multiple layers deep (think of a clay tablet or painting with multiple inscriptions) Encryption for 30 years ago? Trivially breakable with quantum

Shor's algorithm is primarily relevant to asymmetric cryptography, and disk encryption is pretty much universally symmetric. Quantum computers do nothing to break modern disk encryption.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#18

The source code: https://github.com/HighwayFrogs/frogger2-vss I enjoyed skimming through this: https://github.com/HighwayFrogs/frogger2-vss/blob/main/teamS...

Committing ASCII-art of a scantily clad woman is quite the power move.

Re: How Frogger 2’s source code was recovered from a destroyed tape [video]

#20
post #9

Earlier quoted context omitted.

Regardless of the parent's statement, just normal compute in 30 years, plus general vulnerabilities and weaknesses discovered, will ensure that anything encrypted today is easily readable in the future. I can't think of anything from 30 years ago that isn't just a joke today. The same will likely be true by 2050, quantum computing or not. I wonder how many people realise this? Even if one disagrees with my certainty,…

>normal compute You are underestimating the exponential possibilities of keys. >plus general vulnerabilities and weaknesses discovered, will ensure that anything encrypted today is easily readable in the future. You can't just assume that there is always going to be new vulnerabilities that cause it to be broken. It ignores that people have improved at designing secure cryptography over time.

From a security perspective, I argue ypu must assume precisely that.

An example being, destroying sensitive backup media upon its retirement, regardless of data encryption.

Post reply on HN