| Either a changeover in security certificates is a part of the plan with the whole blog/forum changeover thingy that’s in the works, or the security certificate is expiring because someone just plain forgot to renew it. Maybe the whole ‘community platform’ changeover was timed to coincide with this certificate expiring, or maybe it really is a coincidence.
Let the guessing games begin! 9 Responses to “Second Life blogs security certificate expiring”Leave a ReplyCommenters are to be civil, courteous and respectful to others, insofar as it is possible to do so. Beyond that, you're not required to agree with the opinions expressed by me or by others. Think for yourselves! First time commenters will wind-up in the moderation queue and your comment won't appear right away. Ditto for anything that gets flagged by the anti-spam rules. Got a news tip or a press-release? Send it to news@taterunino.net. | Support us...or use Flattr  | |||||||
Dwell On It is proudly powered by WordPress
Entries (RSS) and Comments (RSS).
© Tateru Nino. All Rights reserved.
Tateru Nino and Dwell On It are trademarks of Tateru Nino. Your local laws provide the conditions for your fair and reasonable use of these marks.
All other trademarks are properties of their respective owners.
Page optimized by WP Minify WordPress Plugin
The whole thing, turning off blogs and forums for a week for the migration to the new platform and now the security certificate expiring is just so unprofessional. Healthy companies don’t give off this sort of vibe.
IMHO very few of Linden Lab activities can qualify as professional. I imagine easily that the security warning issued by several browsers when trying to access the blogs will scare off many of those not aware of the impending changeover.
@Thibaud Well, if they don’t know already, they’re certainly unlikely to find out now, given the big scary warnings.
I’ve filed JIRAs about LL inadvertently letting SSL certs expire before, I believe.
No this doesn’t surprise me either.
Slightly unrelated but… browser related…I have had trouble logging in with Safari for over a year now, when I complained there was some temporary fix so I could get in, but the problem is ongoing, there must be a bug in the works somewhere. When you consider how big Safari is, you would think it would have been sorted by now.
Here’s another guess: they might have fired the person who would have checked that.
There isn’t anything automatic to remind a *company* that a security certificate has expired. Some individual has to remember to check. Also, It’s no big deal to renew it.
So I’d say it’s a coincidence.
That said, I don’t understand why LL needed a gap in coverage… unless they have to acquire a bunch of new servers and those servers didn’t arrive in time. Jive was hosted, I believe, on Jive’s servers, so unless the archive’s going to be hosted there as well, LL will have to migrate all that stuff to their own servers.
I imagine that migrating data, converting it for whatever new system there is, and then testing that it hasn’t screwed things up could potentially take quite a while. A lot of links might potentially need rewriting if nothing else.
http://kanomi.blogspot.com/2011/02/private-security-contractor-pitched.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:%20blogspot/tinydancing%20(T%20I%20N%20Y%20%20%20D%20A%20N%20C%20I%20N%20G)
your all nuts… these folks have no control over any part of the systems they spew….
So, let me get this straight – the error has now been eliminated…. by removing session security for folks logged into the website who visit the blog. Great.
I would say that that is probably the worst of the available options that could have been chosen.