I sympathize with developers who throw up their hands and say, “I don’t do security stuff.” No matter what you choose, there’s a trade off that could go wrong. It’s especially troublesome if one deploys a “security website.” I’ve deployed security education websites in many environments over the past 20 years, and I rarely achieve the security level I’d like.
I wanted to watch a security webinar today. But the webinar requires Adobe Flash, in which security researchers seem to uncover 1 or 2 vulnerabilities a month. I discarded Flash when upgrading my OS a couple years ago. It’s ironic that a security webinar might tempt it back onto my machine.
Continue reading Tiptoeing Through Vulnerabilities
A few weeks from now I’ll throw the switch and redirect Cryptosmith web traffic to its new home.
For now, cryptosmith.com still goes to the old site, though popular content and the RSS feed go to the new site at b.cryptosmith.com.
It’s ironic that I’m moving to WordPress. My first site with a modern content management system was a self-hosted WordPress site several years ago. I migrated to Drupal a year or two later. I’ve had a terrific time with Drupal as a plaything, but I’m tired of maintaining it. My son Alex did web software for a few years and tried hard to move me back to WordPress.
Continue reading Migration Round Trip
I am moving my Cryptosmith web site to WordPress.com. This will give me a lot more time to work on content while wasting a lot less time on mucking with the site.
There are things I love about Drupal, but I hate having to manually replace a bunch of files each time they revise the core modules. I’m terrified to think that I might need to migrate from Drupal 7 to Drupal 8 someday. It was awful migrating from 6 to 7. So I’m jumping ship.
Cryptosmith.Com will now reside at WordPress.com. I couldn’t find a Drupal service that was anywhere as cost-effective as WordPress.com.
The old stuff is available at old.cryptosmith.com and cryptosmith.org.