Flash player 11.1 broken by DCOMsoft SWF Protector 3

November 18th, 2011 4 comments

After upgrading to Flash player 11.1 this week (11.1.102.55 to be exact) I noticed that a number of my games and applications were no longer displaying correctly. The screen would either be blank on startup or after a couple of button presses, and after that point right-clicking on the stage would present me with a “movie not loaded” message and not much else.

At first I thought that Adobe had simply dropped the ball again. It wouldn’t be the first time, let’s be honest.

I considered reverting back to a previous player version but of course that wouldn’t solve the problem for everyone else who is using my applications so I decided instead to investigate.

One of the applications that was affected was a personalised video messenger I’ve just finished for a major UK greetings card company. The strange thing was that the application would work on some screens when it was in normal mode, but not at all when it was in debug mode. The only difference between debug mode and normal mode was that for the benefit of the non-technical staff at the card company the application would output its traces to a text field at the bottom of the screen. No other logic was different so naturally my first thought was that it was related to dynamic text fields or maybe an embedded font issue.

After some messing around it turned out that it wasn’t the text field or the embedded font at all. In fact in turns out that Flash player 11.1 is happy with all of that stuff: until you run the SWF through SWF Protector 3. At that point the SWF again either refuses to work at all or refuses to work on screens that use dynamic text fields. For every Flash player version prior to 11.1 the SWF works fine so I can only assume that either there is a bug in 11.1 that SWF Protector 3 exposes or Adobe has deliberately changed something that happens to trip up this particular obfuscator.

So, I’ve had to consign SWF Protector 3 to the bin and am now using Kindi SecureSWF which, although technically a more secure product isn’t as user-friendly as there is no batch import of SWFs and no option to have the protected file over-write the original. I’m actually hoping the next Flash player resumes its compatibility with SWF Protector 3, but with SWF Protector 4 due out for PC any minute now there is also hope that DCOMsoft can resolve the problem themselves.



Gareth Jones, fashion designer

October 30th, 2011 No comments

Over the last week or so I’ve received a LOT of traffic from people searching for a Welsh-American fashion designer called Gareth Jones.

This post is just to confirm that I am not that guy.  :)



Installing an OCZ Vertex 2 SSD in an HP Mini 210

October 15th, 2011 2 comments

You may recall that I upgraded the RAM on my HP Mini 210 to its maximum 2GB back in March – a process that, thanks to the Mini being incredibly fussy with its memory took no less than three attempts in all.

Around a month ago I realised I wasn’t really using the Mini as much as I had thought I would when I first bought it, and after some thought I decided it was because the machine just wasn’t quick enough even with the RAM upgrade. Booting up and logging in took a few minutes and launching Firefox once I was in seemed to take just as long. This meant the machine wasn’t really the convenient there-when-you-need-it computer that I had intended for it to be. This was a shame because the machine itself is really nice – both aesthetically and ergonomically.

My initial attempt at working around the hardware’s limitations was to install Jolicloud, a Linux operating system that uses HTML5 apps to breathe life into older hardware with its modest system requirements. While Jolicloud was significantly faster to use than Windows, I wasn’t entirely happy with this solution as a) I actually really like Windows 7; and b) most of Jolicloud’s “apps” are actually just website bookmarks which to me just seems like cheating.

So, what I did was perhaps a little crazy – I ordered an OCZ Vertex 2 SSD from Scan. I already had a Vertex 3 in my desktop and a Vertex 2 in my laptop and had been incredibly impressed with them both – indeed, the Vertex 2 in my laptop had transformed the machine beyond recognition just a few months before.

The drive arrived a few days later and I quickly set about installing it. I had also ordered a USB3 caddy from eBay to turn the old drive into a portable HDD, and while Windows was installing again on the Mini I setup my new portable HDD as a portable development drive with all of my work mirrored on it from SVN.

Before taking out the original HDD I ran a benchmark which I also ran on the Vertex once the Mini was all set up. The results are quite amazing: with a linear read speed of just over 30MB/sec, a random read speed of just over 3MB/sec and an average access time of 8.74ms the original drive scored 3,637 points. The Vertex performed on an entirely different level with a linear read speed of nearly 134MB/sec, a random read speed of nearly 53MB/sec and an average access time of just 0.27ms to post a score of 495,793.

The Mini now feels like a different machine. It boots in seconds, logs in instantly and opens Firefox pretty much as soon as I’ve released the mouse button. I now use it all the time! According to Windows Experience Index, the bottleneck is now the CPU with a score of 2.4; the SSD has a score of 7.7 and everything else on the machine sits between 3 and 5. I can’t upgrade the CPU as it’s soldered to the motherboard, but to be honest there’s no need to – the Mini was intended as a convenient web browser and emailer, not a gaming rig, and it now does both of those tasks (and a few more besides) pretty much instantly so who cares if the balance of power is a little uneven inside?

The Vertex was perhaps overkill on a 1.6ghz single-core netbook like this, but what a difference it’s made! Also, I can always swap things around again if/when I get another machine in a few years as it’s not like the Vertex has been welded in or anything. Or at least that’s how I justify it to myself!



Toshiba Satellite 320CDT

October 5th, 2011 2 comments

Back in 1998 when I was 16 my father bought me my first Windows computer – a Toshiba Satellite 320CDT laptop from PC World in Chester. It had a 233mhz Pentium MMX CPU, 32MB of RAM and a 4GB HDD with Windows 95 installed.

Although new to Windows, it didn’t take long for me to realise that Windows 95 sucked quite hard. I upgraded to Windows 98SE at the earliest opportunity and boosted the RAM with an additional 64MB taking it to 96MB in total. For the next few years I used that little laptop extensively and I learned a lot from it.

Tired of BSODs I eventually upgraded again to Windows 2000 which offered a much more stable environment at the notable expense of speed and responsiveness. Eventually it became time to upgrade to a desktop and the Toshiba was handed down to my younger twin sisters who, as it turns out, thoroughly abused it.

I dug out the machine while at my parents’ house a couple of weeks back. I was quite mortified to find the keyboard and screen covered with various bits of food, the modem cable was missing, the track pad nipple was missing, the little door covering the PCMCIA slot was missing and the charger socket was loose which meant the laptop would only charge if you held the cable in at a certain angle. Considering I had always kept the machine in good order I was not impressed. I decided to rescue it in the interest of nostalgia and brought it home with me.

The first thing to do was get all the food stains off it, which was quite easy with some wipes after taking out the keyboard. Next I got onto eBay and found a replacement modem cable, track pad nipple and PCMCIA door. I ordered one of each and then set about fixing the loose charger socket. I doubt I’ll ever use the modem again as I have a wireless network card that will fit this, but it’s better complete than incomplete nonetheless.

After finding a service manual for the laptop (mirrored below) I was all set. I opened it up to discover that the machine had obviously been pulled around by the cable as the solder was cracked and broken on BOTH pins! No wonder charging was so hit-and-miss! A little touch-up with a soldering iron and that too was fixed, though I now know why my sisters have gone through no less than 8 charger cables between them with their new laptops – and it isn’t anything to do with the quality of the cables which is what they claim the problem to be!

Over the next couple of days the various replacement parts arrived and eventually the laptop was as good as new – apart from the Windows installation which was full of all kinds of freeware/adware/spyware. I decided to reformat and re-install, which was easy as I’ve kept ISOs of all my OS disks over the years.

Interestingly Windows Update no longer works for any browser older than Explorer 6 SP1. As Windows 2000 comes with Explorer 5, I had to find an offline installation executable to manually update that before I was able to download the other 100+ updates required through Windows Update!

After hours and hours of downloading and installing updates I now once again have an as-new Toshiba 320CDT laptop, fully up-to-date (as far as Windows 2000 goes anyway) and ready to go. It’s too slow to use every day, but as it’s where it all began for me I do feel much better having restored it to its former glory.

If anyone else is restoring a 320CDT, here’s a list of resources and software that might be of interest:



SkyNet distributed computing platform

September 15th, 2011 No comments

As I have more than a passing interest in astronomy and astrophysics, when I read this BBC article about how astronomers want to use idle home computer power to help trawl through terabytes of data I knew at once that I was definitely up for taking part. I made a mental note to download the client as soon as I had some free time.

Well, tonight I had some free time so I Googled SkyNet. Naturally I got a load of Terminator movie references, but a link two or three results down pointed to the Skynet Research Distributed Computing Platform. I opened it up and checked out the terms of service for the tool before installing:

Skynetresearch.com is a website controlled by Warner Brothers Entertainment, Inc. (“Warner”) and is presented in association with the release of the motion picture “Terminator Salvation.” Site and related content, including Skynet Research, are fictional for entertainment purposes. Enjoy! To operate the application, you must have Adobe Air version 1.5 or higher. By downloading this interactive application, you consent to our Terms of Use [link] and Privacy Policy [link] and consent to the use of your information for Warner and the Warner Bros. Entertainment Group [click to link], themselves or “on behalf of Skynet Research” to send you updates and other information concerning “Terminator Salvation” and “Skynet Research” and via the application, subject to our Privacy Policy [link]. Should you wish to unsubscribe to such updates and information, please check the “unsubscribe to all updates” checkbox on the application splash screen. Unsubscribing will not affect your ability to use the application normally.

Well that certainly didn’t look right! I looked up at the URL and yes, I was at warnerbros.com! This was obviously some kind of viral marketing tool for one of the Terminator movies. I hadn’t even looked at the URL before as I had just assumed by the title of the search result that this was what I was looking for and the look of the website did nothing to suggest that I was in the wrong place. I closed the window and went back to Google.

The next link in the list was this one, a WordPress article that encourages people to take part in “furthering Skynet’s understanding of humanity”. Pretty fluffy and yes it linked to the Warner Bros website so clearly an extension of the above marketing campaign. However when I looked down it became apparent that at least one guy seemed to think that he was installing the SkyNet tool featured in the BBC article as he mentions having installed the SETI@Home tool in the past. It seems that an unfortunate choice of name has made the client that several willing participants are looking for difficult to find.

Eventually I found the correct website and in an effort to point anyone else who is interested in taking part in the right direction, the link you need is http://www.theskynet.org.



Nintendo 3DS officially becomes the worst console launch in history

September 13th, 2011 2 comments

On March 25th, 2011 Nintendo officially launched the 3DS in Europe at a price point of £229. It was launched at midnight and after spending the run-up thinking I’d buy one within the first couple of weeks, at around 11.30pm the night before I decided to drive down to ASDA in St. Helens to pick one up at launch.

I got there at 11.55pm and was the only person there waiting to buy one. Odd, I thought, but nevertheless great news as a) I wouldn’t have to wait for long and b) I’d be guaranteed to get one. I picked up the graphite version with 6 games – Tom Clancy’s Ghost Recon Shadow Wars, PES 2011, Super Monkey Ball 3D, Super Street Fighter IV, Ridge Racer 3D and Rayman 3D. Only Street Fighter stood out as a must-have game with the others all being a bit average, but with nothing else available for the console beggars couldn’t be choosers.

Around midnight just as I was paying for my items another guy turned up to buy one, followed by a couple of teenagers who also picked up a unit. It was hardly the rush that the gaming press had been predicting.

Six months on and the games haven’t really picked up. Apart from Zelda and maybe Resident Evil there hasn’t really been anything worth buying, which is crazy considering this is the follow-up to the DS – the most successful console in recent history.

The woeful supply of games and the steep price point of the console were obviously having an impact on sales because on July 28th Nintendo announced a global price drop of around 30%. Acknowledging the console’s performance as a relative failure (though it has still sold a significant number in its own right), Nintendo president Satoru Iwata and other senior management also handed themselves significant pay cuts – an example that we can only wish many a banker would follow.

Such a drop in price so soon after launch is unprecedented and was a sign that Nintendo officially recognised that things were not going according to plan. In an attempt to make up for the ~£100 extra that early adopters had paid for the console Nintendo came up with the Ambassador Programme which entitled users to 20 free game downloads on the Virtual Console. Although better than nothing, many 3DS early adopters – myself included – would have preferred a refund in all honesty.

As if the 3DS’ first six months on the market haven’t been disastrous enough, Nintendo has today announced a new peripheral that adds a second analogue stick to the console. It requires its own AAA battery and will be released on the 10th of December in Japan for around £12.

Home consoles have made use of dual analogue sticks for some years now. The idea first appeared on the N64 in 1996 but was refined to the more familiar design that we have today with the original PlayStation’s Dual-Shock controllers in 1997. Since then pretty much every home console has had them – even the Wii on its classic controllers.

In 2004 Sony released the original PlayStation Portable (PSP), and since then every time rumours have circulated of a redesign or a revamp the gaming community has pretty much begged for a second analogue stick as it makes FPS games in particular a lot easier to play. Sony resisted such calls throughout the lifetime of the PSP but has thankfully implemented the feature in their follow-up, the PlayStation Vita.

So, since the games industry has been asking Sony for dual analogue sticks on its PSP for seven years, one would have thought that any competing company who had a hand-held console in development would have made sure to include such a feature on their new hardware. A company that has led an industry worth billions both with its home console and hand-held would surely have its finger on the pulse and any widely-requested feature like this was bound to make it into the new hardware.

In a move that was either stupidly incompetent or cleverly deliberate, Nintendo chose to ignore seven years of such requests and include just one analogue stick on its 3DS. Spectators were forced to conclude that Nintendo’s intention all along was to use the bottom, touch-sensitive screen as a second analogue as some games had done on the original DS. However, the launch of this new peripheral demonstrates in no uncertain terms that the lack of a second analogue stick on the 3DS was in fact an act of stupid incompetence after all, because Nintendo has now decided that a second physical stick is so important that it justifies an add-on that not only has no elegant way of communicating with the console (there are no expansion ports on the 3DS so it will probably use the infra red port which would also explain why it needs its own battery), but when held symmetrically will shift the screen over to the left of the user’s field of view.

Shifting the console over to the left like this could be a problem because the 3D effect on the 3DS only works in a very narrow viewing angle and games that require motion controls can already push the user outside of it with enthusiastic use. By shifting the screen over by an inch or so the angle will be even tighter on one side.

The botched, home-made look of the console with the expansion attached is a far cry from the simple elegance of the DS Lite (though the original DS of course was no looker) and would suggest that a 3DS redesign is on its way; one that includes the second analogue stick in a more elegant fashion as should have been the case the first time round. This will probably be announced just after Christmas after Nintendo has cleared as much original 3DS stock as possible beforehand.

With that in mind it seems even more foolish for Nintendo to reveal the expansion now as it can only serve to dampen the sales figures that the console is getting since the price drop. It would have made much more sense to keep it under wraps until after Christmas when the redesign is unveiled, maximising sales of the current design for the holiday and providing Nintendo with an elegant new design to market while offering early adopters a way to play the games that will obviously take full advantage of the second stick. As it is, Nintendo is left with an ugly contraption to promote as its primary offering for three months to an audience that would surely rather wait for the inevitable redesign – while Sony will no doubt start marketing its drop-dead gorgeous PS Vita to stick the boot in.

Nintendo again only has itself to blame for the market so confidently predicting a redesign. For years they have capitalised on selling multiple revisions of their previous hand-helds as a means of generating new money for old rope. The DS gave way to the DS Lite which gave way to the DSi which shared the market with the DSi XL. Each version has also shipped in numerous colours and special editions, and even before the DS we had exactly the same scenario with the Game Boy. But never before has a redesign come so quickly after the original machine’s launch.

With such a long list of mistakes and poor decisions relating to the 3DS coupled with the poor response to the Wii’s follow-up the Wii-U, it seems that Nintendo has been riding high on a wave of success for the last five years through happy accidents and good fortune rather than any kind of deliberate strategy. I just don’t see how one company could have got things so right with one console and so wrong with another if the decisions behind them both were all deliberate calculations and part of the same overall vision. Rather than outwitting their competitors with genius decisions it seems Nintendo simply stumbled upon an open goal by accident and happily took advantage of it. With that once-open goal now packed full of other players and Nintendo left relying on outplaying the rest of the field for victory, it seems they’re not quite the gaming gurus they’ve made themselves out to be.

So, where does this leave the current 3DS? With several companies delaying software releases due to the poor console sales which are themselves a result of a lack of quality games (and its previous high price point), the console now faces an up-hill struggle to secure critical mass in the run-up to Christmas. It’s unlikely that the 3DS could completely fail with the vast reserves of cash that Nintendo has amassed over the last 5 years, but I’d say it’s highly unlikely to replicate the success of its predecessor because as lucky as Nintendo seems to have been over the last 5 years – and in light of their recent form it does appear that luck factored significantly in their success – everyone’s luck runs out eventually.



Adobe Media Encoder components have different versions

September 10th, 2011 No comments

For a while now I’ve been greeted by the following error message whenever I run Adobe Media Encoder: Adobe Media Encoder components have different versions. Please update Adobe Media Encoder. Checking for updates failed to resolve the issue as Adobe Updater insisted each time that I already had the latest version of everything installed.

After Googling the error message I discovered that it boils down to a problem with the original 5.0.1 installer and that Adobe has since issued a new installer that fixes the problem, but they’ve left the version number at 5.0.1 so the Updater isn’t picking it up. They did this because the contents of the patch are identical so it’s not an update per se, which makes sense, but it still leaves those who updated with the original installer having to scratch their heads and find the solution themselves.

So, all you need to do to get rid of that error message is re-install the patch with the updated installer. The 32-bit Windows installer is here and the 64-bit installer is here.



DCOMsoft SWF Protector 3

August 27th, 2011 7 comments

Company: DCOMsoft
Product: SWF Protector 3
Price: From $39.95

Following my recent re-review of Amayeta’s SWF Encrypt 6.0, here’s another look at SWF Protector 3 from DCOMsoft.

The latest version of the software is 3.0.1.191 which means it hasn’t changed at all for over a year, so it will be interesting to see if it still offers protection against decompilers that are advancing all the time.

First the interface. In the default simple mode this is clean and quite minimalist. You have a button to add individual files, a button to add folders and a button to recursively add folders which is a nice feature that can save a lot of time on larger projects. After adding your files to the list you can either protect them individually or all in one go.

A properties window on the right gives you rudimentary information on each file while a log window at the bottom keeps you informed of progress.

When protecting a file the program will attempt to use default obfuscation settings which it will automatically wind down if there are any problems so that the resulting file always works. If a file does ever break during the process there’s an advanced mode that allows you to tweak the obfuscation applied to each function individually, though to be honest I have never needed this as the automatic settings have never broken a file.

Obfuscated files are given the original file’s name while the original file is renamed which is great news if you’re obfuscating large projects as it means you won’t have to go round renaming files or updating references afterwards. This was something I highlighted in its predecessor as a major advantage over SWF Encrypt last year, before Amayeta shamelessly copied the feature.

The program does occasionally crash and when it does it will be one of two ways – either immediately after loading up despite no interaction from yourself or immediately after you add a file to the obfuscation list. Resolving the issue in both instances is a simple case of closing the program and running it again, but of course such a crash is an annoyance that can’t really be justified in this day and age of tried and tested OSes, drivers, middleware etc.

So, how does it perform when it comes to obfuscating? For this test I again used Sothink’s SWF Decompiler (version 640, build 3450) and Burak’s ASV 2011 (version 2011/08).

First Sothink’s SWF Decompiler. This tool opened both SWFs without crashing or throwing up any error messages, but the AS it gave me was all obfuscated. In both AS3 and AS2 it seemed to only show me the code as SWF Protector 3 wanted it to be seen, which is what we want from an obfuscator really. When I attempted to rebuild the AS3 FLAs the tool crashed, and while the AS2 files did yield FLAs they was completely worthless as none of the code was intact and the library assets were a mess. In short, all I could get from SWF Decompiler was the audio, fonts and graphics, but none of that is realistically going to help someone rip off your Flash project.

Burak’s ASV fared much better with AS3, but slightly worse with AS2. It was completely thrown by the AS2 files and gave me nothing but a long list of error messages. I couldn’t browse the file properly, let alone rebuild an FLA. This implies that the AS2 obfuscation in SWF Protector 3 is significantly more effective than that found in Amayeta’s SWF Encrypt 6. AS2 is traditionally easier to obfuscate than AS3 though, so how did an AS3 file compare? AS3 was a different story as ASV was not only able to open the file but it also showed me all of the code in original, unobfuscated form. It wasn’t quite able to get all the way through to rebuilding an FLA as the FLA that it exported would not compile into a functioning SWF, but with the asset library intact and the original code all visible in ASV’s code browser, it wouldn’t take too long for a determined developer to put together a working rip-off of your Flash project.

An interesting observation was that the test AS3 SWF increased in size slightly after it was run through ASV, but this didn’t seem to affect the file’s running in any way. I do wonder what extra data ASV injected into the file though.

To conclude, if your SWF files are AS2 then SWF Protector 3 looks like an excellent purchase. The two most well-known decompilers on the market couldn’t even get close to decompiling the files, and this tool costs less than half of what Amayeta charges for its ineffective SWF Encrypt software. If you work in AS3 however it’s clear that although SWF Protector 3 will still protect your work against Sothink’s SWF Decompiler, Burak’s ASV almost has it fully cracked. Indeed, a developer with some time on his/her hands would have no trouble in rebuilding your AS3 project from the exported FLA and unobfuscated code, which means that for AS3 developers the search for the perfect obfuscator continues.

UPDATE: It appears that SWF Protector 3 isn’t compatible with Flash player version 11.1.102.55 and it’s not clear if compatibility will return with a future release of the player. SWF Protector 4 is already out for Mac so it can’t be long before the PC version is made available so hopefully the issue will be resolved soon. Alternatively if you need a Flash obfuscator for PC today then you Kindi SecureSWF is your best bet.



How to disable Skype Home

August 27th, 2011 9 comments

I like to stay up-to-date with my software, always making sure to take advantage of new functionality and security features as soon as they’re available. This applies to Skype just as much as anything else, so a couple of weeks ago when I noticed that Skype had released a new version I downloaded and installed it as I always do.

After installation I loaded the program to take a look and see if I could spot anything new. To my surprise and slight horror, a pretty big window called Skype Home opened alongside Skype itself which I quickly closed, assuming that it was only showing because of the fresh install of the latest version. Just to be sure though I quit the application and loaded it again, and to much greater horror this time Skype Home opened once more.

I had a look around for one of those “do not show at startup” tick-boxes that you sometimes get with stuff like this but couldn’t find one. I opened Skype preferences and had a look in there, hoping to find something similar to the settings in both Windows Live Messenger and Yahoo Messenger, but to no avail. It was then I opened Firefox and did some searching on Google to find various forums full of people lamenting about a new “feature” that Skype have added without any way to turn it off.

A number of things became apparent while reading these forums, such as the fact that Skype did something similar back in 2010 but backtracked in the face of mass protests from their users – so why they would try exactly the same thing two years later and expect a different reaction, I don’t know. Another potentially helpful fact I learned was that the issue only affected users who use Skype in classic view – those who use it in the new, social network-style view are unaffected as Skype Home is built into that interface. I say potentially helpful because sadly it wasn’t of any help to me as I don’t use that view – because it takes up two or three times more screen space.

The bad news was that Skype really haven’t allowed a way to disable the window and with only vague hints that such a way might be provided in the future I was given a choice: either go back to an older version (5.3.0.120 is the latest unaffected version which you can get from here) or find an acceptable workaround. I contemplated rolling back to the previous version but some of the changes in the change-log refer to fixed bugs, and the thought of re-installing software with known bugs didn’t really appeal to me so I decided to search for a solution.

After trying a few different solutions, the most elegant one I’ve found is ClickOff by a guy called Johannes Hübner from Sweden. This tiny little program continuously searches for other programs with defined window titles and performs default actions on them when they’re found. Apparently it was written with the intention of automatically responding to prompts (hence the word click in the name) but another task it’s ideal for is to close unwanted windows such as Skype Home. What makes it better than some of the custom-written programs out there that are specifically designed to target windows called “Skype Home” is that ClickOff will also work for users who use different languages. It can also be used with any other applications that might sometimes pop up unwanted windows (WLM does sometimes, even though I have specifically told it not to) or of course with prompt dialogs that you always answer in the same way.

Why am I posting this article today? Well yesterday Skype released another updated version of their messenger, and after the torrent of abuse they’ve suffered over the last couple of weeks I expected them to have included a way to disable Skype Home from within the program – but unbelievably they haven’t! So it looks like I – and many others – will continue to need ClickOff for the foreseeable future at least.

Update: It’s taken the Skype team an awfully long time to resolve this issue, but at long last they have. As of version 5.5.59.119 the Skype Home window no longer opens by default!



Amayeta SWF Encrypt 6.0

July 25th, 2011 2 comments

Company: Amayeta
Product: SWF Encrypt 6.0
Version tested: 6.0.10
Price: £89 / $145

Since so much of this site’s traffic is from people who are looking for Flash-related obfuscating and decompiling, I decided to revisit all of the products I reviewed last year and once again put them all under the microscope in order to ensure that the information contained within the reviews is still accurate.

First, some background on Amayeta is that it’s owned by Jaspal Sohal, the same guy that owns MDM which makes Zinc. Zinc is a Flash projector that has received a lot of negative press mostly relating to quality and support problems, and with that in mind I must admit I wasn’t expecting much from SWF Encrypt but nevertheless have reviewed the latest build as objectively as possible.

Loading it up

SWF Encrypt 6 takes about 5 seconds to load up on my hefty PC which is quite surprising considering the minimalist interface. The layout of the UI is simple and functional, with all options within easy reach. The window is split into three main areas. A (somewhat clumsy) file browser takes up around a third of the space on the left, a list of SWF files within a given directory takes up the top half of the 2/3 on the right, and settings/properties/logs take up the bottom right 1/3. I’ve attached a screenshot.

The good news

The niggles from last year’s review version are all gone. You can customise your obfuscation preferences to either favour file-size or obfuscation strength, you can over-write the original file with the obfuscated file and two bugs that I discovered last year have also been fixed.

Now the bad news

Unfortunately the removal of last year’s niggles are made pretty much redundant by the fact that what is currently the latest version of SWF Encrypt 6 doesn’t work. I obfuscated some test files using the application’s default (recommended) settings and this is what I found:

Sothink’s SWF Decompiler (version 635, build 3363) was able to rebuild the source FLA and give me access to all of the file’s assets, though the code itself was still obfuscated. Burak’s ASV 2011 (version 2011/07) on the other hand was able to rebuild the FLA along with all of its assets and source code – and it even generated the original class structure for me as well. All I had to do was hit publish and I had a SWF that was identical to the original.

Even changing two out of the three advanced settings (encrypt names advanced and encrypt namespace) failed to stop ASV – and bear in mind that the more of these kinds of settings you enable, the more likely you are to experience problems when you have multiple SWFs working together.

Finally I enabled the third setting, encrypt resources, which did manage to stop ASV because it completely broke the SWF. With this setting enabled, all I got from running the protected SWF was a flashing blue box in the top left with some white symbols inside it. I also noticed that the original file’s size had gone up by 22kb – despite overwrite original filename being set to false – and it no longer worked. SWF Encrypt insisted that the original file had not been touched, yet it had clearly added 22kb of data to it and in doing so had broken that file as well.

Conclusions

So, what we have in SWF Encrypt 6 is a SWF obfuscator that fails to protect your SWFs against one of the best-known SWF decompilers out there on all but the very highest setting, but on that setting it completely breaks your SWF files and even breaks your originals.

Clearly, you’re better off saving your £89 and uploading unprotected files than buying this software from Amayeta. Perhaps the latest version of SWF Protector 3 – at less than half the price – can help? I’ll have a re-review of that up soon.