Firstly, not all possible malleability vectors are "fixed" in 0.9, so transactions are still quite malleable and the transaction ID can still change. The other thing is that they've made the changes to isStandard(), which is a function that checks for standardness and not for validity. In other words, very new nodes won't relay or mine tx's that already exist but have been modified and rebroadcast, but most of the network (like 90%) will.
Furthermore, there are pools like Eligius that mine non-standard transactions (ie. transactions that would fail these new isStandard() malleability checks but are still perfectly valid transactions). Anything relying on a transaction ID in an automated system is fundamentally broken, and harping on "0.9.0 fixes malleability!" is nothing more than an act of desperation.
Oh, and lastly - "the only consequence it will cause the anonymous send to fail" - why would anyone touch a system where an attacker can trivially prevent all anonymous transactions from working?
Your argument is based on the attacker being able to change TXID of every anon transaction?
Can you do that? Is it that easy? or you just saying that some genius hacker can if he really tries?
Last time I checked, even Bitcoin is vulnerable if an attacker spends enough money/time to do it. So that's bad also?
We both do not know what securities supercoindev has put in place nor how easy it is to change txid-reliance in code.
Code isn't finished & public beta test hasn't started. So just wait until it's released before making further accusations.
I hate people attacking each other with mostly assumptions and with a completely biased view. It's not productive.