While HPKP — which helps reduce the attack surface for man-in-the-middle attacks against HTTPS traffic — is only supported in a very small handful of recent Chrome and Firefox builds, it never hurts to get ahead of the curve. Especially when it comes to your site’s security.
Great in-depth analysis from Gizmodo covering every last bullshit claim made about Bulletproof Coffee.
It looks like the WordPress security tool WPScan is looking to move away from the GNU GPL license for their software. That’s rather unfortunate, but after reading about companies trying to repackage and sell WPScan as their own work, I totally get where they’re coming from.
Chasing these companies takes time, sometimes a whole day of emails back and forth arguing the intricacies of the GNU GPL while they try and weasel their way out of complying to our license. This takes a lot of my time away from the important stuff, working on WPScan and the WPScan Vulnerability Database. Because of this I decided to add a clause to the license. If you want to sell WPScan you can pay for a commercial license, otherwise you can use it under the GNU GPL.
After a few months with this license it was pointed out to me that the GNU GPL does not allow these kind of clauses. What some individuals and companies decided was a ‘loophole’.
Their new (proposed) license has been posted as a Gist — which I’ve embedded below — and the developers are welcoming feedback.
If you’re schooled in Public/Open Source software licenses and are interested in the future of WordPress security tools, go leave a comment!
Clever forks of WP Engine’s Mercury Vagrant for the “roll your own server” types courtesy of Zach Adams.
I say “forks” because he’s actually crafted two different Ansible playbooks. One deploys WordPress, HHVM, Percona, PHP-FPM & nginx to a server of your choosing while the other adds Varnish, Memcached & APC to the mix.
I have a vested interest in folks signing up for service at WP Engine — seeing as how I work there and all that — but this is still pretty fantastic.
When logged into MyFitnessPal, all of the pages transmit over insecure HTTP. Everything you eat, your body measurements, your daily activity, and any activity imported from third party services are all transmitted insecurely over HTTP. If you’re on a public wi-fi network, anyone can easily intercept this private health information.
Even worse, if you manually change the logged-in URL from insecure HTTP to secure HTTPS, MyFitnessPal forces you back onto insecure HTTP.
Ew. Guess it’s time to switch to Lose It! then…
P.S. HTTP Shaming is full of some pretty surprising — and utterly heinous — behavior from companies & organizations that should know better. ᔥ
Love Yoast’s WordPress SEO but hate some of the clutter that it brings to your dashboard? There’s a plugin for that.
This plugin also — as Joost points out — breaks the business model that supports WordPress SEO’s development by blocking the ads for Yoast’s other plugins & services. You can turn the ads back on in Tamer’s options, but that’s still a pretty shitty thing to do. ᔥ
Thanks to Google, you can now quickly spin up an Elasticsearch instance for a few dollars a month. Couple that with WordPress plugins like ElasticPress & ES_WP_Query and you can get some pretty nice performance boosts in places where folks don’t normally bother to optimize.
The crew at interconnect/it makes some quality stuff, so I’m pretty excited to try this out.
In reality we’re taking the same problem of providing too many options and migrating them from the Dashboard to the WordPress Theme Customizer.
Bummer.
Tom McFarlin nails it once again.
Speaking of JavaScript, here’s a Node.js-based client for the JSON REST API that’ll eventually make its way into WordPress core.