Uninstall Captchas?

Software follows a life cycle on a computer, which begins with installation and ends in uninstallation. Uninstallation may happen for various reasons, new version of the software, free disk space for other things. Removing software should be less painful than installation. Software that is difficult to remove is evil. Viruses and spyware/malware typically make the removal process as painful as possible. Oddly enough Symantec does the same thing with their consumer grade “Security Software”.
Are you human?
While working on a computer for a neighbor, I came across a few tool bars and other general junk installed on the computer. Even though tool bars usually are not spyware, there is no reason to have the Google, Yahoo, and ask tool bars installed plus a few others. The uninstallers were one or two click installers, pretty standard stuff. Then came the odd software. No one knew what it was, but it was sitting on the installed applications list. Before uninstalling, the user was prompted to fill out a captcha to prove that they were not a computer. After filling it out the uninstall process proceeded as usual. A second software package had the same sort of thing, but it was a tad more sophisticated. It had animated noise bars. Either way, why are these software writers afraid of automated removal of their software? It is pretty obvious, they wrote malware.

What did it do? Well, the obvious thing was auto spawning and eating up 50% of the CPU resources (the system has a Pentium D 820 processor). It disguised itself as Internet Explorer (Why anyone still uses IE is beyond comprehension). Additionally it would cause periodic pop ups and a odd message alert prompt stating “Windows Explorer” when entering Control Panel.

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT 2.1.4

Announcing the immediate availability of Breadcrumb NavXT 2.1.4. Possibly the last release for the 2.1.x branch, 2.1.4 fixes mainly regressions in features found in 2.1.3. Some regressions were fixed in a hotfix posted previously, but others were not. Now, static front pages should work correctly, again. Top level pages in setups with static front pages will no longer show up as a descendant of “blog”. The post title max length property works as expected, again. All around this should be much better than 2.1.3, which introduced too many regressions.

Next up in 2.2.0, which will come out some time early next month.

You can grab the latest Breadcrumb NavXT from the Breadcrumb NavXT project page.

-John Havlik

[end of transmission, stay tuned]

Yes, I know

There is a regression regarding support of static front pages in Breadcrumb NavXT 2.1.3. It has been fixed with the help of a few alert users. You can hotfix your installation if needed, by grabbing the latest breadcrumb-navxt-class.php from SVN. The cause was some cleaning of the class, which inadvertently removed a branch from a if statement that was not orphaned as previously thought. This obviously will make it into the 2.1.4 release, which will be released before the 18th of July. Version 2.2 will debut in late July/early August.

Later this week a new release of Berry will be available. I’ve fixed a number of bugs, and tweaked the comments form. There seems to be a text size bug that will need fixing before the release is made, look for it on Friday.

MooTools 1.2 was released a week or so ago, thus out dating Mtekk’s Testimonials. I’ll get to work on updating that with some nice fixes along with migration to MooTools 1.2. Hopefully, that can be ready before the 18th. With the release of MooTools 1.2 work on WP Trainer will begin (again). Subcomponents of WP Trainer are already complete, the plug-in part itself is what need to be made, along with an interface of sorts. Deciding on the UI is one reason the project keeps getting deferred until later.

-John Havlik

[end of transmission, stay tuned]

Tagged:
Updated:

Breadcrumb NavXT 2.1.3

It time for the third service release for Breadcrumb NavXT 2.1. This is the second to last planed release for the 2.1 branch, heavy development for 2.2 begins this weekend. There are some fixes with bugs in the core breadcrumb class, especially relating to having a post as a member of both a parent category and one of its children. Some administrative interface cleanup has taken place, and the German translation was resynchronized with the administrative interface. Yesterday was the intended release date however a wait for the German translation to finish synchronizing took place, it is not fully up to date, but by the end of the week the distribution will have it fully updated.

New features to look for in 2.2 include fully customizable anchor structures (yes, that means you can use the rel=”” element for those who want nofollows (I’d advise against using nofollows, but that does not mean we’ll stop you)). Breadcrumb trails will no longer require to contain linked elements (for if you want to have them in your HTML title). Plus a bunch of other things. Begining today the Development build from SVN is considered unstable and possibly broken.

You can grab the latest Breadcrumb NavXT from the Breadcrumb NavXT page.

-John Havlik

[end of transmission, stay tuned]

Iframe-B-Gone 1.1

Announcing the immediate availability of Iframe-B-Gone 1.1.0. This new version’s interface matches better with WordPress 2.5’s new dashboard. A dashboard widget performs quick scans of the default terms (yes terms, delimited by commas) and counts how many infections have been cleaned. Note that even with multiple search terms possible, only automatic removal of iframe tags is fully supported. That said, the WordPress Exploit Scanner may be a more valuable tool even though it does not automatically protect against iframe injections.

-John Havlik

[end of transmission, stay tuned]