Quote:
Originally Posted by copse
The date on the files in web file directory listings for this leak, are 2013. That's the archive itself as posted to the web. I have no idea what the dates are inside the archive, as I've not obtained it to look.
Let's also be clear about how easy it was to find. It was named 'amiga os source code 3.1.tar.bz2'.
Simple logic dictates that if they really cared they could have googled and found it, as many of us did. Much much earlier than this conference tweet "leak" announcement. But no, the it must be protected argument is weak because it provably has not been. That the web file directory in question has only now been taken offline in reaction to this tweet, is irrelevant to the long term previous easily discovered availability.
|
Ahem. Please do not assume that the people involved were negligent or otherwise unfit to attend to the task at hand.
When the leak occured, the contents of the archive had to be assessed: what had leaked, had the AmigaOS4 source code repository been compromised?.
Figuring out if the archive contents had proliferated was not straightforward, e.g. the data was repackaged and published under different names on other servers (and that did not include the various bittorrent seeders).
Then the archive contents wound up on GitHub at possible the worst time, on New Year's eve when it turned out nobody was "minding the store" and would take down the material. It took a week for that to happen.
A press release had to be prepared, too. Nobody likes to read them, but somebody has to make the best effort to explain the situation and the consequences. A thankless task, but still necessary.
The thing is, it is complicated, challenging and on more than one level unfair what fate throws at you at times. Best of luck to you that you may never have to face a challenge such as this.