Blog Post

After finding out how widespread the HeartBleed security issue is, it only made sense to find a Chrome extension to help the situation. There are a number of good ones but we chose ChromeBleed because it also works in Google(s goog) searches, showing which sites may still have server vulnerabilities before you even visit them. Meanwhile, the Lenovo ThinkPad Yoga 11e Chromebook is looking good in tablet mode while Microsoft(s msft) ended its Scroogled campaign just in time to add Office Online app shortcuts to the Chrome Web Store.

Join us for this week’s podcast as we discuss those topics as well as some great new features in Chrome Beta for Android and new Chromecast apps here now and coming soon.

I can attest to the fact that Stopbleed (https://chrome.google.com/webstore/detail/stopbleed/okdekadbjjhbnlmldheinccioijofhgc) is definitely working better than Chromebleed at the moment. I checked and Tony is the one who created the original Chromebleed app. If you check Github, you will see that most of the changes were made by Tony. Any issues that were in chromebleed are now fixed in the Stopbleed version, because I do not have any issues.

Jamie Hoyle and I are the major active developers of Chromebleed. We do have some minor issues with the google search page, but will fix those soon. Thank you for your review. We did release a mirror release called Stopbleed with a newer version. Releases have been a problem due to being under auto review in the store, so there are some delays on releases. This might help the admin users to stay at a current release. These two extensions might not always run the same version, but each version is the correct one tagged in the Github repository. We will try to keep our versions at the latest for the users, but we have little control right now. We want to assure the users that there is nothing malicious about the extension. All code is open sourced on github. We just want to help identify sites with the vulnerability.