3 ms·
I remember reading a certain company (not my current employer)'s data retention policy issued by their legal department. It had a schedule for destroying all bu
by skissane 6y ago
I remember reading a certain company (not my current employer)'s data retention policy issued by their legal department. It had a schedule for destroying all business records. Product source code was in there as a business record – to be destroyed N years after end of support. Made me want to cry. I hope they don't actually do what their legal department tells them to.
- londons_explore 6y agoIf hypothetically, someone were to take a copy of that code just before the business destroyed it, they could do almost whatever they liked with it, because the original business wouldn't be able to prove it was stolen from them.
- skissane 6y agoLet me use Microsoft as an example. (And, I'd rather not identify the company in question, but I can say that it wasn't Microsoft – I have absolutely zero information on what Microsoft's data retention policies might be.) Suppose Microsoft's policy was to destroy all copies of the Windows 3.0 source code. Having followed that policy, they have no copies left. Now suppose an ex-Microsoft employee has a copy of the Windows 3.0 source code in their possession, and decides to distribute it. You really think that Microsoft couldn't prove in court that said source code is in fact the Windows 3.0 source code, even if they no longer possessed any copies of it themselves?
- thaumasiotes 6y ago> I'd rather not identify the company in question, but I can say that it wasn't Microsoft – I have absolutely zero information on what Microsoft's data retention policies might be. While earlier things may have been lost, Microsoft operates a Microsoft museum. Anything they have today is pretty likely to be intentionally preserved.
- mikestew 6y agoIt's been fifteen years since I've last darkened MSFT's doorsteps, but they had an internal server that had everything back to DOS 2.0, IIRC. Now, source code I cannot say with any real knowledge, but the bits were (and I'm guessing, still are) there.
- jojobas 6y agoHow do you suppose they would they do it, especially if all references that the code being Windows 3.0 were removed or replaced with something else?
- jerf 6y agoAll sorts of ways. The easiest one would just be to prove that the person in question didn't have the many thousands of programmer-years at their disposal necessary to make something so large and therefore the only possible source is the one entity that ever did, and used it to make Windows. Since "some guy who leaked Windows" is obviously not in possession of that sort of programmer-power, it's a pretty open-and-shut case. That one is so obviously going to win that speculating further isn't worth much, but there's a lot of other ways we could prove it too based on architectural similarities to the existing binary code (which I presume is not wiped off the face of the Earth), but this one, while quite sufficient to prove the case as well, is more abstract and prone to internet snipers trying to prove their smarts by quibbling about endless leaves while missing the obvious location and sheer mind-blowing size of the forest. But we don't have to go here, because the previous paragraph would do just fine.
- waltpad 6y agoyou probably know about GeoWorks Ensemble? https://en.wikipedia.org/wiki/GeoWorks https://en.wikipedia.org/wiki/GeoWorks also: http://toastytech.com/guis/bbe.html http://toastytech.com/guis/bbe.html Wouldn't MS also have to prove that the code is not a derivative of some other PC desktop solution of that era?
- skissane 6y ago> Wouldn't MS also have to prove that the code is not a derivative of some other PC desktop solution of that era? That would be pretty trivial. If you had the Windows 3.0 source code, you could compile it, and the binaries you'd get would be the same as the shipped binaries. (Your version of the source code might not be exactly the same version as the shipped binaries, but even if not 100% identical, a binary diff or disassembly would should great similarity.) Even if someone has modified the code a bit, there would still be immense similarities there, which would be difficult to explain as anything other than copying. Also, GeoWorks and Windows 3.0 have quite different APIs. If you find code exposing an API which is bug-for-bug-compatible with Windows 3.0, then it almost surely is a derivative of the real Windows 3.0 source code. It could be a derivative of some compatible implementation of the Windows API, such as Wine or Sun Wabi, but neither of those would be bug-for-bug compatible; and, as jerf pointed out, a defendant which claimed that they (or someone else other than Microsoft) wrote the code from scratch would have to provide some evidence that they (or someone else) actually carried out the Herculean task of creating a bug-for-bug compatible clean room clone of the Windows API. And not just the application-level API – Windows 3.x has heaps of internal APIs, which largely weren't used by applications and which newer Windows versions don't support (for example, the legacy Windows 3.x device driver models) – any modified copy of the Windows 3.x source is going to support all that, a clean room reimplementation is unlikely to do so. Courts decide civil cases on the basis of the balance of the probabilities, and such a claim must be viewed as improbable, unless some concrete positive evidence is put forward to demonstrate it is true. (IANAL, but you don't need to be a lawyer to know that Microsoft would win this one.)
- jacquesm 6y agoI sincerely hope that you do not ever put that to the test and I think you should stay miles away from advising people on legal matters. To put it bluntly: you are clueless about this stuff.
- asah 6y agoUm, just compare hashes...
- 0xffff2 6y agoHashes of what?
- technicalbard 6y agoI know companies that live in legal fear of discovery and destroy lots of things that have potential data-mining value. Imagine a firm that deletes all email more than 365 days old...
- kjs3 6y ago365 days? Luxury. Try 90 days. Not kidding.