I’ve had the thousandth aha moment. I found someone’s password. Again! Having seen this cockiness of “it can’t happen to me” for such a long time; Time and again proves just one of the two things – Either people believe they are invincible and do not really care or they just do not know how to generate strong random passwords that can be easily remembered.

I’d give my secret recipe for generating passwords; Passwords that can be written in full public view, will never need to be written down, can be remembered for as long as you’re alive (and mentally sound), cannot be broken by your friends or relatives and passwords that are unique to every place you need them. For the record, my Bank of the West password is “Amazing Amazing West of 2005!” Go figure!

A proof of how quickly time flies asserts itself around this time of the year when it is time to renew the SSL certificate used for SMTP, POP and IMAP services on Exchange Server 2007. It is surprising however that the documentation on how to do so is still scarce and hard to come by, nearly 3 years since I embarked on the original installation. What is more intriguing however -- I end up doing the same mistakes every year. This time, I’m going to outline the  whole process.

Here’s how to use GoDaddy’s SSL certificates with Exchange Server 2007 and ISA Server 2006.

This was bound to happen. But it didn’t have to. For an open source framework like DotNetNuke, so powerful and widely adopted, yet blogging or even publishing an article was an after-thought. In the OpenSource world they say, “The product has to be absolutely top-notch to succeed” and yet instead of harnessing and shoring up on the success of DNN, the Blog module stands there, lackluster in every sense, reeking of neglect, derelict, unending wait  except for the oohs and aahs of what’s about to come in the next version.

Just coz I keep forgetting should mean somebody somewhere is looking for this information too. Just wishing the install process for team Foundation were to be a straightforward isn’t enough. Here, here is the walkthrough just for the keepsakes. No, it is not at all a bad idea to keep source control virtualized, in fact it could be advantageous simply because it can be isolated even further due to the virtual setup.