Comparing a hypothetical science instrument to an old grade of consumer device is poor hype. A better comparison is the 1.4 billion pixel camera on Pan Starrs that has been on the sky for two years now or the 340 megapixel CFHT-Megacam that has been on the sky for over nine years. If LSST is delayed much longer, a 3.4 billion pixel astronomy camera will sound like 8 megapixels in an SLR does today: obsolete.

Essentially: how to use an open-source license for something created within a closed-source framework? Clearly it's possible and it happens often with code developed for a closed-source language (like IDL or Matlab for example) but Sharepoint is not really a programming language and I don't know if your creative work can be extracted in a way that it can be licensed separately. I think that's what other comments were getting at by suggesting that you create meta-code like a how-to. That's probably a good idea if Sharepoint does not let you extract your site as an unencumbered expression of your creative work. I think liability or potential for profitable derivative works are pretty much non-issues for something like this but a GPL is a good idea if you can get your work into a form that you have the right to license.

I didn't find any discussion of what may have caused the lack of randomness. Presumably it was a particular implementation on a particular platform of RSA key generation and presumably they know what it is. I would be interested to know too.