Oops

A while back I mentioned that Dragon Stones was now available on Amazon.com and BN.com, but Long Before Dawn hadn’t arrived there yet.  I recently took another look and LBD still wasn’t out in the big stores.  So I went back to Lulu and took a closer look at the project and noticed that, way down under the “price” section, it said something to the effect of “To be set when your book is approved”.  So evidently I forgot to click the “Approve” button after getting my last proof of LBD way back in, oh, April was it?  Just think of all the millions of dollars in sales I’ve lost because of that!  😐

Anyway, I have now clicked the “Approve” button, so Long Before Dawn should be showing up on Amazon.com and the other outlets soon.

No Comment

Seeing as how I like to bash Windows now and then, I thought it would only be fair for me to note a colossal security flaw in the Debian Linux distribution (which is the basis for, among other things, Ubuntu, which I use) affecting the OpenSSL encryption software program.  This isn’t a bug in OpenSSL, but rather, it’s something that a Debian programmer did to it that amounts to, shall we say, an orchiectomy.  Basically, in order to stop some code debugging/profiling tools from complaining, somebody commented out a line of code that was evidently responsible for creating entropy (pseudo-randomness) in order to generate an unguessable encryption key.  Oopsie.  As this is not a technology blog (and I am far from a cryptography expert), I won’t get into the nitty-gritty of what happened; for those who are interested and are of a technical bent, some good articles are here and here (and here, too).

You might’ve heard of SSL.  It’s what’s used to, among other things, broker secure (“https”) connections to web sites.  I’m not sure how bad I made this issue sound, but however bad you think it is, it’s actually worse.  (On the other hand, being open source software, we at least actually know what happened to it.)

And I still don’t have a virus, Google.