No Finished 64-Bit QuickTime X For You! Mac OS X Lion Still Requires QuickTime 7

--
In the true spirit of Apple users, I get seriously pissed off when Apple screw up badly. And OMG has Apple screwed up this time:

In a rather wacked-out article by FairerPlatform, we learned that Apple is only barely upgrading QuickTime 10 in Mac OS X 10.7 Lion. This forces We-The-Technos to continue to (I can't believe this) STILL INSTALL QUICKTIME 7.x.

I can't vent my frustration and rage any better than what I posted over at MacDailyNews:

A very well deserved RANT at Apple:

OMFG APPLE! WTF is wrong with you guys that you STILL CAN�T FINISH QUICKTIME 10!?!?!?!?!

This is when Apple users justifiably get PISSED-THE-HELL-OFF at Apple.

Let�s get real here:

1) There never has been any �QuickTime 10.0.x�. There has only been QuickTime 10.0.0.0.0.0. Apple dumped QT 10.0 on us in 2009 and left the buggy thing laying there with no improvements to follow! THAT SUCKS!

2) Now we apparently are going to get a mere token of an upgrade with 10.1.0 that still cannot come close to the functionality of QuickTime 7.x Pro, therefore, we STILL HAVE TO INSTALL QUICKTIME 7.x!!!!!! THAT SUCKS TOO!

Besides the CRAP functionality of QuickTime 10, and the fact that QuickTime 7.x is only 32-bit, there is one other CRITICAL reason to RANT for Apple to actually FINISH QuickTime 10:

SECURITY!!!

Q: What Apple software has the single WORST SECURITY? It�s not Mac OS X folks.

A: It�s QUICKTIME as in QuickTime 7.x!

MOVE YOUR LAZY ASSES APPLE and FINISH 64-bit QUICKTIME 10 RIGHT NOW!!!! It should have been finished A YEAR AGO!!!!!

I hope other Apple users are equally pissed off at this stoooopidity from Apple. (And folks, I NEVER troll).

Did I adequately get my annoyance across? Will Apple be adequately shamed? Do you think Apple will get the clue that I noticed their laziness?

Clearly, this is NOT going to be the year of full, 64-bit secure Quicktime. The waiting drags on and on...

:-P
---

Critical Adobe Security Patches Arrive, Again

--
I just gotta rant for a couple paragraphs:

The most disappointing thing I learned this week is that Adobe knew about this current crop of security holes last December, 2008. So why are we only learning about it now and only getting patches now. Didn't I say Adobe sucks?

And isn't it amusing that Adobe patched up one slew of security holes last month, and waited on this slew of further security holes. What do they do over at their offices? Argue about whether to patch? How to patch? When to patch? How long can they delay it without people saying 'Adobe sucks"? I know they have a messed up work culture over there. Get with it dummies!

The Patches:

1) Adobe Flash Player v10.0.32.18. There is a special patch for version 9 users to v9.0.246.0.

2) Adobe Air v1.5.2

3) Adobe Reader v9.1.3 - Theoretically available Friday, July 31

4) Acrobat v9.1.3 - Theoretically available Friday, July 31

NOTE: Verify which version you have downloaded. Adobe often don't mark what specific version you are downloading. Instead they may tell you that you are downloading "the latest version" when in fact you are NOT. You need to DIY update whatever you downloaded to the actual 'latest version'. Adobe provide no warning whatsoever. Adobe know about this problem and maybe will stop this practice in the future.

As I say ad nauseam: We're still in the Stone Age of Computing, and in the future they will pity us for the clunky junky stuff we had to put up with. (o_0)
--

Update: The State Of Trojan OSX.RSPlug, aka the 'Porno Trojan'

The net-cracker effort to bring the 'RSPlug' Trojan horse from Windows over to Mac OS X continues apace. As of this week we are now up to version E, aka Trojan OSX.RSPlug.E. Again, this Trojan is showing up at scam pornography websites.

The difference with variants D and E, however, are particularly nefarious. Instead of the Trojan itself being the full payload of malware, it downloads the actual payload from the Internet. This means the Trojan can install literally anything into your system. It's not just for DNS forwarding phishing scams any more.

Of course, it will be possible to kill off the payload Internet sites one by one as sub-variants of D & E pop up. But once infected, a Mac could theoretically become zombied, which these days is the prime goal of net-crackers. Botnets can make big money. As was popularly reported last week, the taking down of one particular bot wrangler killed off as much as 70% of SPAM distribution for a few days. That's a massive botnet. Imagine the profit the bot wrangler was pulling in. Sadly, the botnet involved remained intact and another bot-wrangler stepped in to take advantage of it, restoring SPAM to its usual blasting volume.

You can read the details about Trojan OSX.RSPlug.E over at Intego's website.

One hilarious flagging giveaway of this Trojan is the continued laziness of the developers' social engineering method. Instead of altering their tease line to potential wetware victims, they left it exactly the same as the Windows version. This means that anyone who is both Mac and Windows savvy will realize immediately that something screwy is going on. The blunder is the tease line "Video ActiveX Object Error". For those who don't know, ActiveX is a scripting monstrosity perpetrated by Microsoft several years back. Yeah, it was another of their attempts to make the Internet proprietary. ActiveX is entirely irrelevant on Mac OS X, thank goodness, as it is a gigantic, wide open door for malware infection on Windows. The only web browser on Mac capable of running ActiveX rubbish is FireFox, and you have to specifically install an ActiveX extension. Therefore, for the moment, if you run into a "Video ActiveX Object Error" on a website, you have just run into an attempt to infect you with the Trojan OSX.RSPlug.
--