Let me quote a part of our generic terms of service about Force Majeure:
Tibanne Co. Ltd., agents, partners, ICANN, the central registry nor any person involved in the registration will be liable to the customer or any third party for any direct or indirect loss of profits, earnings or business opportunities, damages, expense, or costs resulting directly or indirectly from any failure to perform any obligation or provide service herunder because of any Force Majeure, or governmental acts or directives, strikes, riot or civil commotion, war, hacking, any natural desaster, equipment or facilities shortages which are beeing experienced by providers of telecommunication services generally, or other similar force or condition beyond Tibanne Co. Ltd.s reasonable control.
And another one:
For all services of Tibanne Co. Ltd. liability will be limited to intention and gross negligence.
We had no intention of getting this to happen, and we have followed every industry standard to make this secure. Despite this it happened. We have learnt new things (especially that lots of people want Bitcoin to disappear).
Giving access to areas of a database that are not needed for an auditor todo their job is 'groos negligence'. There is no reason why an auditor needs access the the hashed passwords. What are they going to do check to make sure the hash is correct and why would there be a need for doing so? This would mean that you have a special section on the site for checking the hashed password or god forbid access to the source code.
This is going to be a tought lesson for you and those involed. I think we need to know who this auditor is. Those that want to might want to take action against the auditor.
With that said, I have yet to do business with Mt Gox. But it wont stop me. I am of the opinion that when this set back runs it course that Mt. Gox will be the most secure of the exchanges. It might not sound like it, but Im on your side MagicalTux.